19 Feb '13, 7pm

"It is literally impossible to impose a convention on a community."

Rails claims that convention over configuration is one of its core principles. When Rails first arrived, in many instances, it took the greatest ideas and most common use cases of Web development, streamlined them, simplified their developer interface, and repackaged them within cleaner APIs. There are certainly exceptions, but at that time, "convention over configuration" accurately described a sizeable majority of Rails design decisions. Calling convention over configuration a core principle of Rails was, at that time, in my opinion, entirely accurate . In its early incarnations, Rails replaced configuration with convention in a very literal way — for instance, using code generators to automate database migrations, because there's nothing more ridiculous than endlessly typing the same things over and over again. When Rails imposed its new convention of RESTful APIs, back...

Full article: http://gilesbowkett.blogspot.com/2013/02/the-lie-of-conve...

Tweets