3 ms·
No, but then you find out you don't need OOP either.
by coldtea 4y ago
No, but then you find out you don't need OOP either.
- pjmlp 4y agoDynamic dispatch and parametric polymorphism are also part of OOP.
- coldtea 4y agoYou can have both without OOP (at least not in the sense of a hierarchy of classes, or any C++/Java style), so...
- pjmlp 4y ago"In the sense of a hierarchy of classes, or any C++/Java style)" is not the point of view of SIGPLAN, ACM or IEEE research about how a OOP language is supposed to be. As a former OOPSLA attendee, I rather fallback on their opinion.
- coldtea 4y ago>is not the point of view of SIGPLAN, ACM or IEEE research about how a OOP language is supposed to be. Which is neither here, nor there. It's how OOP is thought of and practiced in real life by the statistically significant majority, so that's above what Alan Kay thought it should be or what SIGPLAN or the ACM or IEEE thinks "how an OOP language is supposed to be". Terms take their meaning from actual mass usage, not from their inventors or what researchers think they should refer to.
- karmakaze 4y agoI recognized the limitations of class- rather than object-based OOP early on and was glad to find out that's not what OOP was meant to be. Now I understand when people say OOP they mean class inheritance and not much else. Still useful for graphical widgets and some other places where inheritance works well.
- pjmlp 4y agoAlan Kay defined one way of doing OOP, which was already a departure from Simula, and both of them are two measure data points on the OOP tree of language design. Most mass users don't have PhD papers in language research, and whatever most think is wrong.
- coldtea 4y ago>Most mass users don't have PhD papers in language research, and whatever most think is wrong. Just not when it comes to language. OOP as a term is what programmers (majority) uses the term to refer to. In language you can't go wrong using a term as the majority does it - with language not being prescriptive, and being all about communication and shared meanings, and such. That's so strong that even established words, idioms and terms will change definition if they started using differently (awesome doesn't mean "inspires awe" anymore, and dictionaries have had "literally" as also meaning "figurativelly" and used for emphasis, since before we were born). If having "PhD papers in language research" is a prerequisite to use a term "correctly" and the majority uses it otherwise, then the term has long changed meaning. That doesn't change just because a term is technical, as technical terms are also shaped by shared mass usage, not origin or etymology. People with PhD's in linguistics agree. So OOP as commonly used is useful to understand what most other programmers mean, is useful to understand how most programmers who think they do OOP write code, is used in books about "OOP programming", is how the term is used in introductory classes about OOP, and is how people understand OOP in the most popular languages such as Java, C++, Python, and so on (even Javascript, where prototype inheritance is often seen through OOP lens). And OOP "the real meaning" (itself still debated between what Kay meant, what Simula set, and other definitions) is only useful to refer to a set of historical ideas out of use today, to talk to a few people with "PhD papers in language research" and to agree with other pedants.
- pjmlp 4y agoThere is what common people think they know about, and there is science.