this post was submitted on 01 Sep 2023
329 points (96.1% liked)
Programming
17433 readers
294 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Oop is overrated
I never can understand classes
Wow, nice hot take!
I find the concept super intuitive, like a blueprint or a mold.
It's intuitive until you realise that not everything fits in a single inheritance hierarchy.
This gives a good example: https://www.youtube.com/watch?v=wfMtDGfHWpA
I think of OOP as encapsulation, abstraction, and polymorphism primarily. Inheritance is definitely taught as part of it, but it seems like most people have found that to be the least used part of it.
It seems like you understand oop, but find it overrated, from your post it sounded like you didn't understand it -- but maybe you meant you didn't understand it's popularity.
I absolutely understand OOP, its explosion took over everything that took a long time to recover from.
The problem with OOP is that it's pushed as a cure-all both by teachers who do not the problems it solves and also do not understand its own limitations.
In almost every situation where OOP makes sense, something else makes more sense to use.