DEV Community

Discussion on: Java vs Go: Impressive solutions for invented problems

Collapse
 
leob profile image
leob • Edited

Java the language is okay, but everything "surrounding" it (tools, frameworks, ecosystem) is horribly overengineered - just look at tools like Eclipse or Maven, or frameworks like J2EE and Spring with their infinite "flexibility" and configurability (99% of which you rarely need, if ever).

I think the Java world never learned the mantra "less is more".

Collapse
 
jawher profile image
Jawher Moussa

Exactly ! It's not the language, it's the mindset around it.

Collapse
 
siy profile image
Sergiy Yevtushenko

Well, I think maven should not be in this list.

Thread Thread
 
leob profile image
leob • Edited

Hmm I beg to differ, I think Maven is also more complicated than it should be (compared to package managers in other languages like npm, gem, composer and so on).

But maybe that's not entirely Maven's fault, Java's build process is a lot more complex than for the other languages (which largely don't even have a build process), and Maven is of course not just a dependency manager but also a build tool.

Thread Thread
 
siy profile image
Sergiy Yevtushenko

Well, Maven is definitely not a simple tool to grasp and use efficiently, but it extremely powerful and versatile while still rather compact and fast. What is even more important, it's one of the most reliable build/dependency management tool in the long run. It's hard to underestimate this property for projects living for many years. Fancy attempts to replace Maven (I'm looking at you, Groovy) do not hold this property, unfortunately, although they somewhat address Maven steep learning curve.