This article is glorious:
Real-world enterprise software demands a complex set of rigorous and compulsory requirements pertaining to the expected amount of embedded abstractions within the software solution. In other words, object-oriented programming enables the programmer to utilize multiple mechanisms of abstraction that fully satisfy the complex requirements demanded by the enterprise.
This was my favorite.
It takes at least 20–30 years to get good with OOP. Even then most people with 30 years of OOP experience haven’t truly mastered it. The learning path is rough, filled with uncertainty. A lifetime of learning awaits the OOP developer, how exciting is that?
I won’t admit how long it took me to realize the article was satire
I think that is a valid point. I’m eager to create my first FP app because I’m curious to see how I feel about the experience compared to an OOP app. I already have an idea of the things I might like …and things I might miss or find an inconvenience.
This should also be a hint.
Nobody can really take this as a real rant… isn’t it ?
It is obvious that so-called “functional” programming is flawed, it makes redundant things like refactoring and unit testing unnecessarily easy. This, in turn, will act as a distraction to the development team — they might accidentally waste time on those useless activities, instead of delivering new features.
This example clearly demonstrates the inferiority of functional programming — it makes refactoring too easy:
Well said. The man has more to say, f.e. (“most popular of my blog posts on Hacker News”): https://naildrivin5.com/blog/2011/08/01/why-i-wont-work-for-google-twitter-facebook.html