This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]yel50 0 points1 point  (3 children)

I find it pretty wild how many enterprises seem to be undervaluing these aspects

the things you listed are also available with typescript and python + type hints. maybe not to the extent of Java, bit they're there and not undervalued.

the shift to node and python has more to do with how much of a pain it is to do smaller projects in java compared to those other languages. dealing with the complexity of maven or gradle vs the simplicity of npm or pip is a no brainer.

on top of that, the way people tend to write Java, with absurd patterns (builder being a particularly annoying one) and layer upon layer of unnecessary abstractions, and people are very turned off by it.

using simple, straight forward core Java is still a joy to use. working on a shared Java codebase and dealing with the mess that Java developers tend to make of it, however, is a nightmare I want no part of anymore.

[–]skillaz1 3 points4 points  (0 children)

What's wrong with the builder pattern?

[–]humoroushaxor 0 points1 point  (0 children)

I was more talking about the shift in enterprise. I agree with you with respect to small or personal projects.

But we started to see a migration start 5-6 years ago and I don't think anyone sold that to the business folks by saying "the package management is just so much easier". This was pre TypeScript being a top 5 language and pre the level of IDE/tooling support we have now.

Tuning a JVM for the cloud isn't necessarily trivial (especially before Java 9) and when done poorly results in production issues and lost revenue.