The things that are hard to beat about the Java world is the ecosystem, the tooling and the package management. Stuff more or less works without too much hassle, there's often a good library for what you want to do, and you're building on decades of previous industry work.
In terms of package management, the most unreliable parts of our project are Node and Python.
both can be proxy-cached on your local network to remove external dependencies.
both have ... uuuh... okay package managers (poetry/pipenv for python, npm/yarn for node) with *.lock files to properly define their dependencies. How does this differ from maven/gradle?
honestly, i prefer the node/python package management. Maven/Gradle is just so incredibly extensible making it insanely powerful.. But it comes at the cost of complexity and developers being unable to actually understand whats happening.
The JVM is now better than ever, the language is modernized, the library ecosystem is excellent. If you don't like the systax, alternative languages are well-developed and intergrated.
Even maven which is imho terrible to set up is a nice tool and the amount of libraries and tooling coming with it are amazing.