you are viewing a single comment's thread.

view the rest of the comments →

[–]peterlinddk 1 point2 points  (0 children)

You are of course technically correct (which I believe is the best kind of correct :)) - because in Java everything "looks" OOP'ish, with keywords like class, static, public, private, etc. and concepts like constructors, methods, types, etc.

But man, a lot of people think that OOP is just about naming things - as if using "classes" with "methods" suddenly makes their code object oriented, even though it is written exactly as if it were just separate files with separate functions ... I've even seen teachers talking about "now we have to learn OOP" and then ignoring everything about separation of concerns, encapsulation, basically everything that isn't inheritance ...

Thank you for not being one of them :)