I don't think this article is particularly well-written. However, I do agree with the conclusion. For web-based programming, object oriented programming is simply ridiculous in all but a small number of cases. That's why the Lampshade framework I wrote is purely procedural, and why I'm able to write software on top of it so quickly. Client-side GUI programming is a different story, in my opinion.
In general, just because you're capable of understanding complex, abstract concepts doesn't mean that it's always best to use them.
For web-based programming, object oriented programming is simply ridiculous in all but a small number of cases.
Agreed. Functional programming seems to make a lot more sense. Fundamentally, isn't a web server just a function f: url -> html? Sure, databases and sessions complicate things, but even in these cases, functional structures seem a lot more elegant (in a mathematical sense) than OOP ones.
For any programming, OOP brings some advantages. What you might be decrying is over-the-top abuse of OOP patterns. Certainly, for most programming, abuse of design patterns is unwarranted.
However, taking, as an example, Ruby, which is both a functional and OOP language, the OOP features make the language a lot nicer.
Anyway, that article is completely daft. And I refuse to take any advice about programming from someone who spells "linear" as "linier". Shame there's no down-mod button.
> However, I do agree with the conclusion. For web-based programming, object oriented programming is simply ridiculous in all but a small number of cases.
I read his conclusion as that object oriented programming has failed us because it is too hard to understand, and we need a new, simpler, more accessible, dumbed-down programming paradigm. He is advocating programming for non-programmers, which has been tried many times before and has always met the worst kind of failure (universal disdain by "real" programmers).
I would say we've had it for a while now. Ever seen the things that people on a trading desk do with Excel? Or maybe VB, when they get daring.
Generally something that gets the job done that they want it do.
However, it is not going to be very extensible, no one besides the person who wrote it will be able to understand it (and maybe not even him), they will have no idea what to do if they want it to go faster, or if they need to make it work on the web, or integrate some data feed that doesn't have any easy way to import into Excel, or...
In summary, we have programming for non-programmers, it works as well as can be expected, but sometimes you really, really need a programmer.
In general, just because you're capable of understanding complex, abstract concepts doesn't mean that it's always best to use them.