Why would anyone use this shitty language?

Why would anyone use this shitty language?

Attached: 1557640951022.png (1948x858, 152K)

OOP != Java

This isn't an OOP thing, it's an enterprise thing. When you yourself make a project nobody is forcing you to make a bunch of interfaces and abstract classes, just make what you need.

Just use assembly, anything else is having mommy hold babbies hand

grandpa, cobol is also a shitty language

inheritance was a mistake

> He dosn't write directly in machine code
Pleb.

>subhuman
>fleas 14
lel

The image is clearly directed at java.

Smalltalk and Common Lisp define OOP in a much better way than Java and C++.

>use this shitty language?
wew lad

>write enterprise system
>has to interface with ten other custom-built retarded system
>has to implement poorly defined requirements specified by retards
>system lives for ten years, the original developers are long gone, no-one understands what shit does anymore

The structure and modularization provided by OOP and design patterns is the ONLY thing standing between you and suicide

Attached: hy84qi98qap21.png (846x563, 382K)

(You) can write shitty code in any language.

(OP)
This isn't just the issue of java, the oop is cancer and noone knows how to implement it properly. I've observed a large C# codebase at work, and it's a shit show of factories, controllers, etc. and nothing ever works. People break encapsulation interfacing with objects they aren't supposed to, write static dictionaries and methods that fuck up parallel execution.

ExceptionCatcher sounds more like AOP than OOP

Why is getting the same haircut a zoomer thing? Maybe following shitty hair trends but what adult wants to run the risk of getting a shitty cut?

Most would admit now that C++ isn’t really an OO languages. Generic programming and user defined types are its defining features.

>external logging framework
keked

The thing that sets CLOS apart from other object systems is it's generic methods, and theres nothing particularly OO about them. Haskell has multi parameter type classes to do multimethods.

>he doesn't turn transistors on and off individually
kek

Three reasons:
>inheritance
>polymorphism
>encapsulation
OOP is a programming paradigm not a language. It's a style of programming.

Inheritance sucks balls in nearly every wau
Subtyping is the worst kind of polymorphism
OO encapsulation works well but is tedious

examples of OOP: unix programming environment, golang, erlang

used by people who don't understand it

I have the repos to prove it too

Easier to offload the bulk of the work to Pajeets.
The only reason it caught on.