Why is Object Oriented Programming so widely and commonly used

>>56374686
Memes and indians.

>>56374799
Don't forget the 12 year old savants who are in your college programming class.

>Structured programming class
>fucking Java
>they're credits so i gotta take it
>"Alright today we're gonna make a program that makes arrays without a set lenght"
>spent 2 hours making classes and chaining them together
>it took me 15 minutes to do it all over again in C using pointers.

fucking java.

>>56374686

its because our brains is wired to understand concepts as objects and their relations. everything around you is objects.

a professional would ofc use the paradigm that fits the project the most. its not always objects that is the best structure. but most often i would say it is.

>>56374862
>>spent 2 hours making classes and chaining them together

That just shows that you're stupid

>>56374862
Wow what a fucking retard

>>56374862
Look at this retard

>>56374686
>i fail to understand the problem
>object oriented is broken
guess what if one is not retarded and notice that the rank should be a field inside the class Person instead of being an entirely different kind of person every problem goes away

>>56374686
Because nearly everyone fell into the hype back in the 1980s. Now people regret wasting time on it... but people hate to admit when they are wrong, so they stay with it and coerce others. Bad.

"object oriented" is a vague term

record types are handy for clumping related info together
packages are handy for modulatiry and hiding implementation details from an interface.

I admit I don't user inheritance very much. I often wonder why more folks don't use templates.

>>56374862
>what is arraylist

>>56374686
That's pretty easily solved by Mixins, and has been solved since like the 80s. It's just that shitty OOP languages didn't offer mixins for a long time.