Amen. Despite being 25 years old the average JS stack is janky as hell. I regularly do all kinds of nonsense to get JS to work properly.

With Java the code, dependency management, and build tools just work. It's very pleasant to maintain.

Maintaining a JS project over more than a few years is a nightmare. Forced rewrites as libraries, build tools, linters, frameworks, and the language itself are constantly being reinvented. It's a huge pointless drain on resources.

And JS is awful cross-platform. You have to check and polyfill every feature if you want to work outside latest Chrome and Firefox. And transpile the code down to ES5.

With Java it runs exactly the same on every platform. We develop on Macs and run on Linux and it doesn't even matter.

I'm a back-end dev (various languages), and recently did some front-end work with React/TypeScript. It took minutes to 'compile' the 'scripting' language for me to run my changes in my development environment. That was as bad as the worst (mixed Java/Scala) project compile times I'd experienced using a JVM language. Some/most(?) of that might be asset handling, but 'modern' toolchains don't know their own cost or value.