>I believe your case proves the exception of the rule. When talking about Frameworks and coding tools you have to build constantly thinking ahead of time. A framework feature that is not used can easily be ignored in the end product, so you may have a set of classes and you are using just a few of them. Besides you would never know if some of your code is ever used, you have to build the tools by playing all possibilities out in your mind. This is a very interesting task.

Definately not an easy task. But very often the result is wanting a banana, going to the framework Gorilla and ending up including the whole jungle, to cite from JS/Elliot way of thinking.

Which for me translates into using smaller, task-specific tools/libraries/micro-frameworks and writing glue code in an API-like manner so that exchanging such libraries is no big deal.