OOP is just the modern, better marketed GOTO

OOP is just the modern, better marketed GOTO.
Use it well, and the code gets cleaner and more readable.
But very few people use it in that way, and the code end up being a hard to debug and expand mess as you don't even know where the shit you need to work on is without following it closely for hours.

Attached: Za warudo.jpg (633x471, 26K)

Other urls found in this thread:

quitebasic.com/prj/math/mandelbrot/
rextester.com/IQIK72615
rextester.com/NYEJSV28957
jdoodle.com/a/1peC
myredditnudes.com/
twitter.com/NSFWRedditVideo

Is not the same true for every paradigm?

Not all paradigms lead to bad code structure if abused.
They lead to all sorts of other problems, but OO cause pretty similar to GOTO disasters.

Yes, it is

Attached: 8QUEENS_SCRIPTBASIC.png (556x504, 21K)

What a mess

quitebasic.com/prj/math/mandelbrot/

UMA

Im your opinion, what is OOP exactly? Do languages like Python and Golang count as OO languages? Or does Java not even count because it's not "completely" OO?

Classes, inheritance, objects, all that jazz.
Those things are like the goto command.

Attached: huehuehue.webm (320x240, 506K)

nice, user. really nice.

It's quite impressive what you can actually do on the TMS9918 with an modern converter thing.

uncommon bait

In that respect I agree that OOP is a lot like GOTO. Useful when used right, but the issue is it's seldom truly appropriate.

A sickle may be useful a tool, but in a world with combine tractors they're pretty much irrelevant.

I fell for it. Well done

>Use it well, and [it's good]
>but very few people use it [well]
That's practically the definition of everything every entity in the world ever did. No Fucking Shit.

Yes yes, but the goto failure mode is quite similar to the OO failure mode.

Thats basically how you do stuff in asm

rextester.com/IQIK72615
rextester.com/NYEJSV28957

but BASIC is always return, even if had error

bump

jdoodle.com/a/1peC

Attached: XANAX.jpg (685x385, 19K)

> this again
just use lisp

>Not all paradigms lead to bad code structure if abused
all paradigms lead to bad code when "abused". That's what "abused" means in this context.

OO is a very poorly defined paradigm. What is OO? Is Java OO? Is Smalltalk OO? Is CLOS OO?

...