What is that one feature that's missing from your favorite web framework?

Question

There are several very high quality web frameworks out there today, and everyone seems to be able to find one that becomes their favorite. Then, they have nothing but good things to say about the framework in question, and they relate their personal experiences on how the framework has made web development more enjoyable for them.

That's excellent, and the web framework-related questions I've seen on stackoverflow have been answered in helpful ways while avoiding flame wars and so on - that says a lot about the people who participate here and it's a pleasure to read quality content.

So here's my question: sure, there are 99 reasons to love your favorite web framework, but what is that 1 extra feature that you wish it had? Or that 1 area that you think could use some improvement?

Hopefully we've moved past the "my framework is better than your framework" pointless discussions, and we've also realized that all frameworks have their sweet spots. I certainly respect people who can admit that their favorite framework is not perfect, and I'd like to read about the types of features that people find are missing or could be improved. Who knows, the developers of those frameworks might hear you and implement/improve those features!

Thanks in advance for your responses.

Answer 1

I'll post an answer to my own question by admitting that my favorite framework, Stripes, could use some improvement in the flexibility of its localization mechanism. While the mechanism is quite useable, it should be easier for developers to customize which resource bundles are dynamically used and which are the lookup keys for field names and error messages.

But hey, we're working on it!

Answer 2

With ASP.NET the only thing I dislike is that MS often encourages quick and dirty style development with too many drag and drop controls and datasets over better thought through not so quick, but much less dirty, solutions.