Anonymous
7/25/2025, 9:03:23 PM
No.106023323
okay guys I'll bite - can someone explain to me what is the issue with OOP? NO, I don't mean the overcomplicated retarded AstractSingletonProxyBeanFactory-type Enterprise code, but the basic ideas of OOP.
So it's been some time since I learned it, but if I remember correctly, it's that you group relevant data and methods together into objects, define what properties an methods are private to it, and what are accessible from the outside. Add inheritance+polymorphism to it to extend the functionality of certain classes, while still allowing them to act as their base classes, and bam, you have OOP.
What is exactly wrong with this approach? There are plenty of usecases where this makes perfect sense, no?
So it's been some time since I learned it, but if I remember correctly, it's that you group relevant data and methods together into objects, define what properties an methods are private to it, and what are accessible from the outside. Add inheritance+polymorphism to it to extend the functionality of certain classes, while still allowing them to act as their base classes, and bam, you have OOP.
What is exactly wrong with this approach? There are plenty of usecases where this makes perfect sense, no?