[macosxnerd101]

Quote

The time has come for Rubyists in general and Rails in particular to embrace Ruby’s Lisp heritage and ditch YAML as a configuration default for database. Code is Data/Data is Code. There are a host of reasons why Ruby is great for configuration and only a few in favor of YAML. Let’s look at why we use YAML in the Ruby community:

-You don’t have to quote Strings sometimes
-It is better than XML.
-Rails does it in the database configuration.

http://blog.mojotech...ll-the-way-down

[Lemur]

Much further and you might as well just take the plunge and learn LISP itself. Most people comment and say the odd syntax is the key point to not learning it, but it's that very syntax (or lack thereof) that gives it its real power.

Ruby approaches it, and is in quite a few ways a clear ancestor of LISP. I do agree though that the DC&CD is a huge step in efficiency and needs to be capitalized one more. In other news, Ruby is renamed RLISP.

Jokes aside, check into Paul Graham's check list for what makes a LISP and you'll be fairly shocked at some of it: http://paulgraham.com/diff.html

Ruby is quickly approaching, with the exception of absolutes in 6, 8, and 9.

[sepp2k]

Quote

The time has come for Rubyists in general and Rails in particular to embrace Ruby’s Lisp heritage and ditch YAML as a configuration default for database. Code is Data/Data is Code.

I don't see how what's proposed in that blog has anything to do with "code is data". All he does is write code that uses data structures.

[Lemur]

Probably primarily using eval, instance_eval, and other such dynamic code loading.