Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

15
  • 44
    You can't reasonably expect to compare any programming paradigms on such short and contrived examples. Anyone here can come up with code requirements that make their own preferred paradigm look better than rest, especially if they implement other improperly. Only when you have real, big, changing project can you gain insights in strengths and weaknesses of different paradigms. Commented May 10, 2017 at 19:55
  • 20
    There's nothing about OO programming which mandates that those 3 methods should go together in the same class; similarly there's nothing about OO programming which mandates that behaviour should exist in the same class as data. That is to say, with OO Programming you can put data in the same class as behaviour, or you can split it out to a separate entity/model. either way, OO has nothing really to say about how data should relate to an object, since the concept of an object is fundamentally concerned with modelling behaviour by grouping logically-related methods into a class. Commented May 10, 2017 at 20:00
  • 20
    I got 10 sentences into that rant of an article and gave up. Pay no attention to the man behind that curtain. In other news, I had no idea that True Scotsmen were primarily OOP programmers. Commented May 10, 2017 at 20:28
  • 11
    Yet another rant from someone who writes procedural code in an OO language, then wonders why OO is not working for him. Commented May 10, 2017 at 21:45
  • 11
    Though it is undoubtedly true that OOP is a disaster of design missteps from start to finish -- and I'm proud to be a part of it! -- this article is unreadable, and the example you give is basically making the argument that a poorly designed class hierarchy is poorly designed. Commented May 10, 2017 at 22:19