When choosing a framework, I want it to be community supported. This means it's under active development and open to change.
When programming an app against a framework, I want it to simply not break when updating to a point release.
I'm not really interested in a comparison of app implementation details of Rails versus Django. What I'd like to know is the crap I'm going to have to deal with moving from x.2 to x.3. Or y2.3 to y3.0. And how does the plugin/addin/module structure enforce limits and consistency?
And while we're at it, someone come up with more interesting posts than Rails versus Django. Can we get some well written comparisons of, say, a Clojure-framework for apps versus a C# one or a server-side JavaScript one?
When choosing a framework, I want it to be community supported. This means it's under active development and open to change.
When programming an app against a framework, I want it to simply not break when updating to a point release.
I'm not really interested in a comparison of app implementation details of Rails versus Django. What I'd like to know is the crap I'm going to have to deal with moving from x.2 to x.3. Or y2.3 to y3.0. And how does the plugin/addin/module structure enforce limits and consistency?
And while we're at it, someone come up with more interesting posts than Rails versus Django. Can we get some well written comparisons of, say, a Clojure-framework for apps versus a C# one or a server-side JavaScript one?