Web frameworks - looking for QWAN

IPM has published results of the "Pre-requisites of a Good Framework" poll. The answer options were:

• Strong separation of data
• Web 2.0 support and preferably libraries built in
• Strong naming conventions and smart English recognition
• Robustness (ability to handle large volumes of traffic and data)
• Rapid development features (scaffolding etc.)
• A great IDE (preferably Eclipse)
• Others

Christopher Alexander (his works inspired the Gang of Four), described a feature which some buildings possess and some do not. He stated that it is not measureable, but you can just feel it. He called this feature Quality Without A Name (1, 2).

My requirements for the good framework aren't about the technology. They are rather about the feelings I look for when evaluating the framework. They are about the Quality Without A Name...

So here are my Alternative Pre-requisites of the Good Framework:

• gives you well-thought, clean "frames" to work within - easy to understand paradigm of thinking about app, directory stuctures, etc. letting you avoid a "design paralysis"
• makes you feel natural and comfortable when working on the application - eases things, instead of making it harder
• is documented well enough, the docs are not over-detailed, but friendly and easy to use
• doesn't try to be everything for everybody - is focused to solve selected class of problems

Where have I found Quality Without A Name in the world of web frameworks?

• Java - Spring Framework
• Ruby - Ruby on Rails
• PHP - Code Igniter

Of course those choices are based on my subjective feelings (not comparison of features). Every one of them provides its own way of doing things, very specific to the language and the areas of intended applications.