3 ms·

Could we get a (2013) in the title please.

• Cthulhu_ 3y ago
  Makes me wonder if / what changed in OOP land since then; from what I gathered it's pretty stagnant.
  • jghn 3y ago
    Depends on how you view OOP. For instance "The Repeated Deaths of OOP" (2015) [1] notes how the definition of OOP has been morphing over time to match current realities. [1] https://loup-vaillant.fr/articles/deaths-of-oop https://loup-vaillant.fr/articles/deaths-of-oop
  • prewett 3y ago
    My personal opinion is the problem people are solving moved from what used to be called "desktop applications", for which OOP is a good solution, to other problems. Also, the advantages of HTML/JS (cross-platform, ease of distributing updates) is so great that native apps have fallen out of favor. On the server side and for things like ML/AI, OOP is less helpful, hence the rise of FP. Unfortunately, the people developing web frameworks apparently did not have much experience with native GUI libraries, which all work more or less the same, and they decided that a functional programming style with React was the way to go. So now you have a soup of React hooks and JS callbacks that makes code as readable as something with goto everywhere. But each individual page is rarely complex enough for this to make maintenance more than slower / more tedious than necessary. OOP is old-fashioned now. React is the way.