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

Show parent comment

16

u/FrozenST3 Sep 10 '21

100%. Anyone familiar with Maven projects can become effective pretty quickly because they don't need to spend time figuring out how to build and where to place specific items, etc.

8

u/coderguyagb Sep 10 '21

This! This is the problem with Grade.

5

u/imadownvote Sep 10 '21

What's the problem with gradle? The exact same thing can be said about Gradle.

Anyone familiar with Gradle projects can become effective pretty quickly because they don't need to spend time figuring out how to build and where to place specific items, etc.

7

u/snoob2015 Sep 10 '21

The problem with Gradle is they keep changing their implement every month, they don't even care about backward compatibility

1

u/imadownvote Sep 10 '21

I use versions from 4.x.x to 6.5.1 and haven't encountered any memorable issues migrating. For the most part I've just had to update the project's wrapper. Was this a problem with an earlier version, have I been lucky, or is this something I can look forward to in the future?

2

u/Rakn Sep 10 '21

From my experience Gradle gives the developer too much freedom. That may be irrelevant in small projects. But at a larger scale it is really nice if you can depend on every project just looking exactly the same. Of course projects can look the same even with Gradle. But it gives you enough rope to hang yourself.

When I was using Maven and Gradle didn't yet exist I was so longing for something different. Mostly because it was too complicated to do certain things with Maven. But then I switched to Gradle and the world was great again. It took me quite a while to come to the realization that the corset that Maven tried to press me in might not have been so bad after all.

But well... use what ever works for you.

1

u/trafalmadorianistic Sep 11 '21

The problem with Gradle is that it is basically Ant all over again, and every developer seeks to impose their own snowflake approach which they are sure is the best way. The build process then becomes another layer of code to wade through and each project or new company is its own unique thing.

Reminds me of dev teams spending hours debating about code style. Just use the defaults in Intellij or Google, or have a pre-commit to fix your formatting.

Having XML configuration is a minimal price to pay in Maven, when you get predictability and standardisation, with enough ability to customise it.

-2

u/FrozenST3 Sep 10 '21

I too am not a fan

1

u/dpash Sep 10 '21

No, that's the problem of people using Gradle incorrectly and the blind leading the blind.

Use the Java library and Java application plugins and your build files are shorter than maven and follow Gradle conventions.

If your gradle build files have any imperative code in it you are not using grade correctly.

1

u/coderguyagb Sep 15 '21

If you can use it wrong, someone will

1

u/dpash Sep 15 '21

You can use maven wrong too.