Anonymous · original post · 2026-07-23 02:55:51
OOP feels very powerful because it allows you to write a shitload of very simple methods and chain together a billion class and interface inheritance hierarchies to achieve something that feels like it's more complex than the code you actually wrote. It's like "emergent" behavior.
>oh shit, I didn't realize that would actually work
>damn how is that even working correctly
>waow OOP is so awesome because I don't understand how my own code works
This comes at the expense of performance. And when some bug finally does show up you sometimes can't figure out why because you have to step through 10 gorillion tiny little methods and getters and setters to trace code execution.
Report · Quote
Anonymous · reply · 2026-07-23 02:58:27
I think people just hate the overly complicated design patterns than the actual OOP paradigm.
Report · Quote
Anonymous · reply · 2026-07-23 03:00:14
>>26137
Didn't Pajeet introduce those design patterns everyone hates?
Report · Quote
Anonymous · reply · 2026-07-23 03:34:22
>>26136
>This comes at the expense of performance.
What performance? This has never been a consequence of programming ever except on low level embedded programming using C, and even then I know people who use OOP style programming for it. Stop saying shit you dont understand.
Report · Quote
Anonymous · reply · 2026-07-23 03:39:00
>>26063
>RawPizza
Jfc, just make it bool isCooked
Report · Quote
Anonymous · reply · 2026-07-23 03:51:08
>>26139
>i'm always driving with the handbrake engaged and it's never been a problem for me, only race cars care about that
he said while everyone behind him in traffic is fucking livid
you are the reason why the file manager in windows has lag now
Report · Quote
Anonymous · reply · 2026-07-23 06:37:16
>>25916
Fully clojurepilled
Report · Quote
Anonymous · reply · 2026-07-23 07:11:14
>>25886
it's a concept like many others, it has it's use cases and like many others it's used where it's not meant to be used far too often.
Report · Quote
Anonymous · reply · 2026-07-23 07:14:06
oh god i'm ooping it I'm gonna oop
Report · Quote
Anonymous · reply · 2026-07-23 11:26:55
>>26075
Yet another irrelevant semantic fallacy argument. State is data. The distinction isn't relevant as far as the defense and criticism of OOP cult practices are concerned.
Report · Quote
Anonymous · reply · 2026-07-23 11:46:18
>>25886
>For a group project we even made a simple drone show with Python commands.
You have the collective value of an average middle class 15 year old in a civilised nation.
Report · Quote
the-runtime-guy · reply · 2026-07-23 11:57:33
okay, babblers and demagogues, thats it, topic's closed.
the next one >>109348778
Report · Quote
Anonymous · reply · 2026-07-23 11:59:47
>>26147
needy faggot
Report · Quote
Anonymous · reply · 2026-07-23 13:24:37
>>26145
There is no semantic fallacy. It's just you being either dumb or ignorant, and insisting on repeating the fundamental lack of understanding of the difference between state and data.
Furthermore, calling it OOP "cult practices" is clearly a projection of treating programming terms as an object of cult and worship. That's a fallacy.
Report · Quote
Anonymous · reply · 2026-07-23 13:31:08
>>26149
>lack of understanding of the difference between state and data.
State is a kind of data, retard.
Report · Quote
Anonymous · reply · 2026-07-23 13:39:20
>>26149
>understanding of the difference between state and data.
There's no distinction here.
In a program working on file(s), you have new file("./img.jpg), the buffer of the files content is stored inside the class. Is the image buffer now data OR state?
>OOP "cult practices"
He's spot on, there's many programming style religions. They are religions because they discard all practical concerns like ease of writing, objective measures of ease of reading, and performance. See >>26139
Report · Quote
Anonymous · reply · 2026-07-23 13:51:00
>>26150
now that's a semantic fallacy
Report · Quote
Anonymous · reply · 2026-07-23 14:00:22
>>26152
interesting how you dodged
>In a program working on file(s), you have new file("./img.jpg), the buffer of the files content is stored inside the class. Is the image buffer now data OR state?
Report · Quote
Anonymous · reply · 2026-07-23 14:04:51
>please reply to my time-wasting, intentionally ambiguous example
no
Report · Quote
Anonymous · reply · 2026-07-23 14:10:26
The real question is why oopers get so defensive of the term and the ideological territory? Instead of acknowledging the undeniable truth that the OOP ideology and its memes have been inexcusably responsible for a lot of bad habits and shitty code, and merely defending locally valid use cases for specific techniques, they always get extremely defensive. As if they can't just take the good and leave the bad, the NEED the term OOP to be viewed positively because they have invested their whole identity on it.
Report · Quote
Anonymous · reply · 2026-07-23 14:18:41
>>26067
> Are you modifying the state of RawPizza to become a Cooked RawPizza?
Not necessarly. It was just a mindless example but you can leverage dynamical inheritance in prototype based OOP
RAwpizza can be a trait object that change the prototype of a cloned object
Something like this
RawPIzza := Object clone do(
cook := method(
self setProto(CookedPizza)) -- change the prototype of the receiver to Cooked pizza
eat := method( write("you can't eat a raw pizza"))
)
CookedPizza := Object clone do(
eat := method()
cook := method(write("already cooked"))
cut := method(...)
)
Margherita := Rawpizza clone
Margherita eat -- returns "you can't eat..."
Margherita cut -- cannot answer this message
Margerita cook -- now margherita delegates to CookedPizza object and not RawPIzza one (dynamic inheritance)
Magherita cut -- now you can cut it
In a way you are still thinking about it in terms of class based OOP: RawPizza is an object, not a class or a type
It was again a mindless example but you can model it to make actually sense
Report · Quote
Anonymous · reply · 2026-07-23 14:21:07
>>26155
>The real question is why oopers get so defensive of the term and the ideological territory?
No one is defensive of something that is simply a tool in the toolbox, not unlike functional programming. You're making a mountain out of a molehill autistically.
>the OOP ideology and its memes have been inexcusably responsible for a lot of bad habits and shitty code,
No, shitty code has been caused by outsourcing to india, the phillipines, and mexico because I was on the teams having to deal with them. Across reddit and linkedin, there's constant criticism that outsourcing has created very bad codebases, and was likely responsible for the increase in Boeing airplane failures across the world, something that was hardly a thing before the era of outsourcing.
If anything, I've been brought in on more accounts than one to clean up shitty jeet code using OOP principles. What they did had nothing to do with it at all.
> As if they can't just take the good and leave the bad, the NEED the term OOP to be viewed positively because they have invested their whole identity on it.
The only people I know who take it as their philiosophy is unironically indians. They're the only ones who use OOP as a bible instead of a tool, and why all their code ends up a overengineered java mess, even in non Java languages.
In summary, you have no idea what you're talking about and have no real world experience, much like half of /g/.
Report · Quote
Anonymous · reply · 2026-07-23 14:24:07
The problem is purity. Like people come up with cool ideas or paradigms and that's pretty neat, but then some retard comes along and is all like "absolutely everything, every single aspect of this language must adhere strictly to paradigm!" and just, fucking why? Right tool for the right job you know, no point forcing awkward nonsense where it doesn't belong.
Report · Quote
Anonymous · reply · 2026-07-23 14:27:31
>>26154
You won't say because it reveals that you are wrong.
>If you say the file buffer is data, then you must admit objects hold data.
>If you say it's state, then you must admit that everything in memory is state.
>If you say both, you must admit that state is a kind of data.
This is a example to demonstrate that your distinction was not meaningful.
Report · Quote
Anonymous · reply · 2026-07-23 14:37:12
>>26010
it means that he ignores the side effects and says they don't exist
Report · Quote
Anonymous · reply · 2026-07-23 14:37:53
>>26159
thank you for revealing it was indeed an intentionally ambiguous, time-wasting question
all it demonstrated is your bad faith argumentation, though
Report · Quote
Anonymous · reply · 2026-07-23 14:48:32
You'll like OOP when your client wants your program to do anything with anything and swap its component with anything
Report · Quote
Anonymous · reply · 2026-07-23 14:51:35
>>26157
>No one is defensive
>>25919
>>25933
>>25940
>>25946
>>25969
>>26021
>>26157
>No, shitty code has been caused by outsourcing to india, the phillipines, and mexico because I was on the teams having to deal with them.
Both can be true.
Most of the OOP-brained people writing bad object models for simple problems instead of straightforward bottom-up solutions were white (one was trans).
Report · Quote
Anonymous · reply · 2026-07-23 14:52:28
>>26162
Even old C was OOP with how header files worked. In fact, you could organize it so that you had relevant classes based on different header/ c file organization, and it does effectively the same thing. Files just act as classes.
Report · Quote
Anonymous · reply · 2026-07-23 14:52:36
>>26161
What is YOUR point? You're the one pushing the irrelevant distinction between state and data as if it is somehow important to the discussion. Explain why it matters or fuck off.
Report · Quote
Anonymous · reply · 2026-07-23 14:55:29
>>26163
>No one is defensive
You sound like a brainrot libtard. Having an opposite opinion and arguing is not "being defensive" you mongoloid
Report · Quote
Anonymous · reply · 2026-07-23 14:56:38
>>26155
>real question is why oopers get so defensive of the term and the ideological territory?
Because they are dogmatic. That's why we call them things like religious and cult.
>undeniable truth that the OOP ideology and its memes have been inexcusably responsible for a lot of bad habits and shitty code, and merely defending locally valid use cases for specific techniques
The closest I have seen is them admitting that education on the topic being bad (like uncle bobs book).
>>26157
>No one is defensive of something that is simply a tool in the toolbox
lel, its a little defensive, while claiming no one is, which is obviously false.
>caused by outsourcing
Of course it has hurt code quality over all and always will. But it's not the only cause.
In fact the indians being OOP evangelists is a result of the western fixation with it, from it being forced in java to it being a default in education with no mention of it's drawbacks.
There's many, even otherwise good white western programmers that overuse OOP. And many mediocre ones like uncle bob that preach for the worst uses of it.
Report · Quote
Anonymous · reply · 2026-07-23 14:57:14
>>26163
And there's a lot of trannies who support C style coding.
What you're failing to realize is that this has nothing to do with OOP being bad. Has everything to do with just incompetent programmers. Cause ever since the retarded STEM initiative that got pushed back in the early 2000s, everyone thinks they can do it. In reality, programming is not a common skill anyone can pick up. And more people need to highlight that not everyone is going to have the ability to code. Or be smart enough for it. And autists hate on OOP instead of the root of the problem are part of that group of incompentent people cause they fail to understand what engineering is.
That's why the successful ones know all ranges of the industry instead of sitting at home focusing on one little measly paradigm that has nothing to do with productivity or any form of long term professionalism. You are an neet coder/ nocoder and always will be.
Report · Quote
Anonymous · reply · 2026-07-23 15:04:56
>>26162
What component? Give an example.
I mean I can also give examples of where OOP is useful, one would be when actually simulating tangible things, like a game, with many possible configurations that also execute differently. Like moves in pokemon.
>>26166
I don't think he has a point anymore. His original "argument" was
>OOP doesn't couple data and logic as cniles continue to repeat like unresponsive retards
essentially "critics are incompetent because they don't know the difference between state and data"
And when btfo he will call others time-wasting, hahaha.
Report · Quote
Anonymous · reply · 2026-07-23 15:49:48
OOP is how your boss wants you to program so that you can get replaced by an Indian next year. OOP is restrictive and predictable. It turns you into an interchangeable human compiler so when you ask for a raise he can replace you with an immigrant.
OOP is also bad for the same reason global mutable variables are bad. The only difference is that the mess is more localized, but eventually you will run into the same problems.
Your best bet it to pickup a functional programming language before its too late
Report · Quote
Anonymous · reply · 2026-07-23 15:51:30
>>26170
Dude shut up. You have no idea what the fuck youre talking about. No boss of mines has ever said anything OOP related, you lying faggot.
Report · Quote
Anonymous · reply · 2026-07-23 15:55:56
>>26170
>Your best bet it to pickup a functional programming language before its too late
of course it's a functard post
no other kind of poster would dream such unemployed-core stuff up, like a boss caring how the code is written. or the constant fear of being replaced by indians (clearly due to such lack of competences that an indian is a viable, realistic replacement)
Report · Quote
Anonymous · reply · 2026-07-23 15:59:31
>>26172
kek was thinking the same thing.
Report · Quote
Anonymous · reply · 2026-07-23 16:35:25
>>26172
Use your head faggot, if your boss doesn't care about how the code is written the your job is inevitably going to be overrun by the lowest common denominator.
A verbose, mouth-breather friendly language will only accelerate this
Sorry that I want to program with people who know how to use a toilet
Report · Quote
Anonymous · reply · 2026-07-23 16:37:18
>>26174
Usually, youre suppose to have a senior who nips this in the bud. And the industry standard is OOP, and thats because it ended up winning.
Report · Quote
Anonymous · reply · 2026-07-23 16:45:09
>>26174
shit and piss yourself over it all you want, it won't change the fact that actually competent people have no reason to fear being replaced by indians
not like your worries about being replaced have any merit, though, when you're not even employed in the first place
Report · Quote
Anonymous · reply · 2026-07-23 17:35:49
>>26170
This is stupid to the point that it seems like a false flag.
If you want to make a codebase hard to read and hard to change, so that you cannot be replaced, OOP is perfect for you. Especially with clean code (polymorphism everywhere, methods at most 1 line long, nonsensically split)... Add inheritance and you have a really nicely incomprehensible rats nest, and you have institutional support for it.
Hell, actually maybe that's why it's so popular kek
Report · Quote
Anonymous · reply · 2026-07-23 18:02:11
Declarative programming is unnatural.
Report · Quote
Anonymous · reply · 2026-07-23 18:03:28
>Distant past is futuristic dystopia at war
HOLY KINO
Report · Quote
sage · reply · 2026-07-23 22:00:17
>>25886
>why does everyone hate math?
>everyone
Report · Quote