The outcome of Guido’s post wasn’t a surprise really. The majority of the frameworks around, in my opinion, try and do too much. By that very nature, if you don’t want to do something the same way as the author, its often painful to achieve it.

I think that the author’s should be looking to provide a strong, well structured, fast code base. If a developer needs to do something else, they can inherit the base and continue on their way – or use the base as building blocks for something bigger.

I find it surprising that they aren’t writing a base to facilitate growth, reuse and extensibility. Instead, to some degree, it seems they are building something that is leaning towards being coupled. I think that the majority of them aren’t really writing a framework so much, as a content management type solution.

Al.