makes both rust trannies and cnile seethe nonstopwhen did you realize java and oop hate was brown coded?
>>108701652java is literally the most brown language of allIt's also a terrible language. If there's some JVM lib you absolutely need to use, Clojure or Kotlin are better choices.
>>108701652Yeah it's nice but C# is nicer.>>108701672But enough about Python....
The write once run everywhere stuff is really cool
>>108701652OOP hate is zoomer coded. It's the end result of people who learned OOP wrong in the 90s becoming professors and teaching it wrong.
I once hired an Indian to write Ruby. At first I was in denial, his code was like overly complex for no reason and I struggled to understand it. Then it dawned on me this was a combination of Java ptsd, an idea that indians have that more code is better and the fact that he was incompetent. I fired him after a week and never looked back. I'm sure some indians can write nice code and are competent, but they probably have to work extra hard for people to recognize that. With LLMs these days it must be nearly impossible for good indians to have any kind of recognition.
>>108703768Having said that, I don't hate OOP, but Java OOP is stupid. I especially hate interfaces and I hate that Go has interfaces, because it makes no fucking sense.
the superior OOP language.
>>108703777there is rarely a use for interfaces if you own all the code (except for lambda targets). plugging your group of callbacks into a library / framework is usually done via interfaces and they are great for that: describe exactly what you have to provide, usually come with documentation. if only one or two implementations of an interface are passed to the library code, the jit inlines your methods into the call sites (monomorphic or bimorphic), what's not to like?
>>108703777Really depends on what you're doing OP. But I'd be confident enough to say that most apps a single person is making probably doesn't need it. Hell, unless you're extending from some class in the JDK or some external library, I would say you could get away without using inheritance too in a lot of usecases. Java is not a bad language. There is just a lot of bad Java code out there
>>108703855usecase? excluding a TODO app
>>108705122I made a simple web crawler without so much as creating an interface or subclasses. Realistically the only time I ever used a bunch of these abstractions was with a J2EE app or a Spring app. In a lot of cases there was so much abstraction and meta coding with Spring I didn't care too much. But this is all for server side web apps... which honestly I would like to get away from more
>>108701652I feel like you can write nice code with Java, especially modern Java, but man have I ever seen some complete and utter abominations out there in the field.
Hating Java is literally just from retarded plebbit Durgasoft memes made by jeets who think by larping as whites by hating Java people will accept them.
>>108705122twitter uses it
>>108705379USED it. And a lot of it was Scala which is being replaced with Rust
>>108705122netflix uses it, amazon uses it, google uses it, banks use it, insurance companies use it, basically every large organization uses it
>>108705122
>>108701652I keep forgetting Java exists. It kinda doesn't, outside of corporate systems
>>108701652Java itself is alright.OOP is still retarded, although Java's take on it is far less retarded than Sepples'.
>>108703777What do you mean interfaces "make no fucking sense"??? Do you actually care about maintainability or do you just scribble poo all throughout your application? Java interfaces are what allow you to implement most of the good patterns in OOP -> strategy, state, observer, etc.
>>108703777>I especially hate interfacesWow. You should be thinking about and designing everything in terms of interfaces even in languages that don't have them.
>>108707844I like OOP in JavaScript
>>108701652C# utterly mogs it in every way
>>108703777such cool digits, but, holy shit, you are insanely retarded.
>>108708843Except checked exceptions.
>>108702255Python is an excellent language for its original domain of glue scripting and it used to be pretty good for explorative scientific computing.The problem came from people using it for userland gui applications and backend web servers.>>108703703>no true OOPAll the bad parts of OOP are what retards like you promote anyway.Basically, on one hand you have imperative programming, which is more closely aligned with how computers work and how humans intuitively think (a list of steps). On the other end you have functional programming which is more aligned with the way abstract computation works. The imperative end fights the accidental difficulty of hardware. The functional end struggles to get performance through layers of abstraction.Java is the grotesque pile of shit in the middle that combines the worst of both worlds. With java, you get mediocre performance and while fighting the accidental difficulty of human folly and dumb decisions.>>108703768Javadevs are notorious for not being able to program competently in any other language.
>>108703855Defeated by Kotlin
>>108702255C# is just Java with an added layer of pajeet.
>>108709055typical perspective of someone filtered by OOP"it's shit because it's bad because it's shit", never mentioning any specific issues because it would have become immediately obvious it's skill issue
>>108709055>Java is the grotesque pile of shit in the middle that combines the worst of both worlds.not that anon. but OOP is just a way to organize your imperative code.the idea is that in imperative code, instructions usually need some sort of state and parameters. different instructions share some state and parameters. OOP starts by grouping that shared state and parameters with the relevant instructions meant to operate on them.then you realize that some data and state is only meant to be accessed and edited by some of those instructions. and some of those instructions are only meant to be used inside other sets of instructions. and then you get encapsulation. everything else from inheritance and polymorphism arises from that. then all the design patterns.OOP is just a set of conventions to organize your imperative code to avoid your code turnning into spaghetti code overtime.you eventually start treating your code like a set of modular well encapsulated machines that plug into each other in a factory to achieve different tasks.every large project eventually reinvents OOP patterns. even ones written in languages without much OOP features. like the linux kernel.
>>108709301also meant to reply to this anon here>>108709360
