Just checking... You think that code that is less readable and more
tedious to write is an advantage? I guess from the perspective of
macro-optimization vs micro-optimization I wouldn't argue with you,
but I think that's a hell of a way to encourage people to do the
right thing. If going restful is all that, you shouldn't need to
rely on syntactic vinegar to force people to do it the right way.
Now, if you were to say that organizing the actions hash as {:action
=> method, ...} is desirable because it guarantees an action only is
used once, then sure, that makes sense. Either way, I can get behind
it.
I do, actually. And I love the term syntactic vinegar. Consider it stolen ;)
I think syntactic vinegar is one of the best ways to encourage people
to do the right thing. You're basically allowing them to do whatever
they want, but if they're cutting against the grain, they'll have to
suffer ugliness. This means that you can when you must, but won't when
it doesn't matter.
Ruby itself is built heavily upon syntactic vinegar in spots that you
shouldn't be fumbling with too much (like ObjectSpace).
Syntactic vinegar. Love it.
--
David Heinemeier Hansson
http://www.loudthinking.com -- Broadcasting Brain
http://www.basecamphq.com -- Online project management
http://www.backpackit.com -- Personal information manager
http://www.rubyonrails.com -- Web-application framework
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
