4 ms·
I always thought OO was a design philosophy rather than a set of tick boxes that a programming language/notation must provide. Design in OO, code in whatever yo
by EliRivers 16y ago
I always thought OO was a design philosophy rather than a set of tick boxes that a programming language/notation must provide. Design in OO, code in whatever you like, but note that some programming languages make it easier than others.
Obviously my interpretation is no more authoritative than anyone else's :(
- numeromancer 16y agoGreat. Now we can argue over what a "design philosophy" is, and whether OO is one.
- EliRivers 16y agoAwesome. It's your idea, so you can go first :)
- numeromancer 16y agoNo thanks. I'll leave such questions to the pointy-headed meta-academics. I'm a practical philosopher, and I pick the epistemological tools which best fit the job-at-hand, and which give me the most bang for my buck.
- arethuza 16y agoApplication or library design can be object-oriented even though the underlying implementation language isn't - it's just rather easier to do if the language does have direct support for some OO features. Similarly, you can use a language that claims to be OO and ignore and of those features and write purely procedural code.
- coliveira 16y agoYour idea makes sense, but historically OO design came after OO languages. It was a big part of the hype promoted by tool makers during the 90s.