Re:The faster you unlearn OOP, the better for you and your s...
by iainmerrick on Sunday November 25, 2018 @11:05AM
(#18527384)
The OOP that the author "never understood" is what we see ALL the time in enterprise and startup code.
Well, is there a paradigm where you tend to see mostly good code? If so I’ve never come across it. Besides plenty of bad OO, I’ve seen bad functional programming, bad reactive programming, very bad state machines. Bad code is bad code.
(And what other categories of code are you thinking of, besides “enterprise and startup”? Those two would seem to cover a pretty wide range.)
Re:The faster you unlearn OOP, the better for you and your s...
by coldtea on Sunday November 25, 2018 @11:29AM
(#18527476)
>besides “enterprise and startup”
There are several:
FOSS projects like Gnome/KDE can be said are neither enterprise or startup.
Industrial coding (e.g. to control operations in a factory)
Embedded code.
Hobbyist projects.
Games.
Application development (desktop apps and co).
again IMO, demonstrate that the author never really understood OOP.
That's a "No true Scotchman/OOP" fallacy. The OOP that the author "never understood" is what we see ALL the time in enterprise and startup code.
There could be a better OOP (e.g. Alan Kay's definition of it), but that's not what people are taught or practice.