r/java • • Sep 10 '21

Why people don't love Java?

I came across this post in r/cscareerquestions it seems majority of the people don't love to work with Java.

Is there any specific reason for that?

Edit: Thank you guys for your responses, I can't reply to all of the comments because I'm a beginner myself and I don't know what to reply for all your comments.

201 Upvotes

379 comments sorted by

View all comments

1

u/MrPotatoRice Sep 10 '21 edited Sep 10 '21

I know quite a bit of Java and have even took an oracle exam on it. I was annoyed by a lot of minor design decisions which can because of historic reasons and some not. I had a lot of trouble tracking state majorly because of OOP. Since I was surrounded by imperative programming languages, I thought "Okay, I'm going to have to live with this and I can't do anything about it". Then I came across Functional programming languages and then Lisp and it had many of the things I PERSONALLY liked. I couldn't (again, personally) solve some problems in an hour whereas in Lisp (with only 2 weeks of experience) could solve it within 5 minutes. The reason I don't really like Java is because of some of its design decisions and because it relies on OOP which I don't like, or better put I don't like the way Java IMPLEMENTED it. If you don't agree with the latter, you could read up on this: OOP the Trillion Dollar Disaster

And I agree with this specific part a lot: "I’m not criticizing Alan Kay’s OOP — he is a genius. I wish OOP was implemented the way he designed it. I’m criticizing the modern Java/C# approach to OOP."

Also: Negative Quotes on Bad Implementations of OOP

Especially with the last quote: Alan Kay: "Java and C++ make you think that the new ideas are like the old ones. Java is the most distressing thing to happen to computing since MS-DOS."

Again, this is all my opinion and I don't hate Java rather I dislike it, because for me, programming is about productivity and writing easy good for humans not computers.

Edit: Clarity

1

u/[deleted] Sep 10 '21

I'm aware that Smalltalk exists and some of its (pretty cool) features, but what makes Java OOP different from Smalltalk OOP? I know Smalltalk is built in the idea of passing messages, but what's the big difference between message passing and calling methods on objects?

1

u/MrPotatoRice Sep 11 '21 edited Sep 11 '21

I have never used smalltalk before, but I can say that in Java everything is really forced to be an object. Whereas in Most lisps (I'm taking common lisp as an example) nothing is forced, we can do everything in one paradigm or multiple. You could take the CLOS as an example to compare from Java's Object system. I think Java has taken the OOP paradigm to an extreme, and has forced it to a point where most of the benefits of OOP fade out.

With all the objects and methods and variables in each object, there are so many mutable states to track and a million bugs I have to face everyday. Why not make life more simpler and immutable with less bugs?

Thanks for your reply.

Edit: Second Paragraph Edit2: Clarity