I'm not a huge fan of OOP either, but I'm rather much getting tired of these articles who rant on about it from a logically unsound position like my grandfather rants about Obama.
OOP "sucks" because programmers suck. There are a lot of bad programmers in the world. SOme of them occasionally write programming languages, too. So just because certain people fail to create quality projects, or one particular language, written in ancient times, doesn't stand up to scrutiny, doesn't mean the entire idea is flawed.
Modern object-oriented programming (whatever you want to call it, I'm not going to get into any No True Scotsman debates) is a very well-understood paradigm. If you have a set of experienced, skilled developers and nobody is going off trying to do insane things, you can implement many projects with an OO design and it will be very successful.
Not every project is a Boeing 747 or the Sistine Chapel or Dante's Inferno. Most projects are just wood sheds and latrines and gas stations. In terms of grunt-work programming where the problem domain is well understood, OO works just fine.
And FP works just fine. And straight procedural works just fine. And it really doesn't matter. Because the quality of software has nothing to do with your choice of paradigm or programming language or operating system or anything. It is the team that matters. That's it.
And if you're embarking on a massive air liner or an epic poem, your basic choices of tools are once again not going to matter that much, either. It is again up to having the right people. In this case, you need brilliant people, and not just people who struggle to put together a birdhouse without supervision.
OOP "sucks" because programmers suck. There are a lot of bad programmers in the world. SOme of them occasionally write programming languages, too. So just because certain people fail to create quality projects, or one particular language, written in ancient times, doesn't stand up to scrutiny, doesn't mean the entire idea is flawed.
Modern object-oriented programming (whatever you want to call it, I'm not going to get into any No True Scotsman debates) is a very well-understood paradigm. If you have a set of experienced, skilled developers and nobody is going off trying to do insane things, you can implement many projects with an OO design and it will be very successful.
Not every project is a Boeing 747 or the Sistine Chapel or Dante's Inferno. Most projects are just wood sheds and latrines and gas stations. In terms of grunt-work programming where the problem domain is well understood, OO works just fine.
And FP works just fine. And straight procedural works just fine. And it really doesn't matter. Because the quality of software has nothing to do with your choice of paradigm or programming language or operating system or anything. It is the team that matters. That's it.
And if you're embarking on a massive air liner or an epic poem, your basic choices of tools are once again not going to matter that much, either. It is again up to having the right people. In this case, you need brilliant people, and not just people who struggle to put together a birdhouse without supervision.