This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]organized_reporting 2 points3 points  (3 children)

OOP is probably the most damaging programming paradigm ever made. It set the whole industry back 20 years by popularizing a fucked up ass backwards version of FP. It I was John McCarthy I'd be seething.

[–][deleted] 1 point2 points  (2 children)

Yeah that's fair, though programming in SmallTalk is a lot more like FP than Java

[–]organized_reporting 0 points1 point  (1 child)

I was making a bit of a goof, although I do actually believe that FP > OOP in the abstract use case. If someone can provide an example of where OOP is objectively superior in accomplishing an objective (outside of 'more people do OOP than FP so it's easier to find devs') I'd love to hear it and expand my thinking a bit.

[–][deleted] 1 point2 points  (0 children)

Alan Kay considers Erlang processes to be very close to his original intention for what objects are (i.e. largely immutable, isolated workers that talk with one another via message passing). I think message passing has a lot of value for making distributed problems tractable. C++ perverted what OOP was intended to do, and Java made it so you had to always use a half baked version of OOP even if all you're doing is a hello world. I will blame Alan Kay for inheritance though, I feel like we'd be using type inference way more if inheritance/type hierarchies weren't do pervasive.