Web framework Manifesto

While I don't agree with every point, I think the Web Framework Manifesto gives a good sense of some of thing I expect to see in a framework (and plan to include in LightBase). Some of the "independent UI components" while still allowing the back button to "do the right thing" is a pain to implement in a language without closures and a server memory hog in any application, but they are all things I'm pondering for version 2.0 of LightBase (i.e. I'm considering them but not coding them yet). Right now I'm focused on the basics like a DI engine and ORM rolled just the way I like it as well as my page controller model, composable views, automated handling of mapping of form fields for single or multiple object forms and generation of "first cut" of everything so you can just extend and customize if you want.

I think it is safe to say there is still plenty of room for both existing frameworks to extend the scope of what they do and for new frameworks exploring different metaphors. I think there is also a place for frameworks that keep true to a central vision and (for instance) stay solidly in the MVC space. DHH noted that Rails is not the "one true framework" as the more problems your framework solves, the less suited it is to each problem, so frameworks optimized for subsets of use cases will make more sense for people whose use cases consistenly fall within those spaces whereas more generalized frameworks will fit better for people with a wider range of needs who are prepared to spend a little more time on each project in return for a framework that provides them with more flexibility.

I think the next couple of years are going to be really exciting times as we look at all of the frameworks (especially outside of the CF world) and move the CF frameworks world to the next level.

What are you working on or hoping for in terms of ColdFusion frameworks and features?