Great post. I guess in the end it all comes down to “Use the best tool for the job”. And don’t be afraid to mix things if it makes sense. It’s also true that OOP has it’s merits and there are cases where OOP makes expressing your code easier. Usually this is more visible on more complex cases than on simple ones.

And finally about ASP.NET MVC … i love it, even if a big part of it is using extension methods witch are just syntax sugar for free functions. They make perfect sense in the context.

Again, great post and great blog.

I’d agree with you if all these frameworks were written in java or C#. My degree required passes in courses using C++, 68000 assembly, Haskell (and, yes, java), and I think it’s a shame that so many degrees these days are so narrow.

However, some of the worst culprits of the framework/OO lovefest are those using python and ruby, both of which have reasonable functional constructs and don’t require you to use classes (well, not explicitly anyway). Yet still the tunnel-vision remains.

It’s particularly baffling given that Seaside’s continuation-passing style is a genuine improvement in handling complex multi-page interactions over mucking around shuttling stuff to and from the model in typical MVC. Yet, as someone on reddit pointed out recently, Seaside will probably be obsoleted soon by increasingly powerful client-side javascript tools that solve the same problems less elegantly but more fashionably. Shame.

I chose to use the Drupal CMS, and there ain’t a shred of OO PHP in it at all, and I think it’s a very well build and thought out framework.