Right... the way I see it is that mvc's, most notably rails, follow the mantra of 'favoring convention over configuration'... and some frameworks take that idea to the extreme and wind up favoring convention *at the cost of* configuration. Or perhaps the configuration bits are a PITA to work with, because they get no attention.
I think one of the issues with that is that it is quite difficult (contradictory, even) to favor conventions *and* also be inventive. -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
