On Windows with luck 5.3 will be the first version that the compiler actually works, let alone existing libraries that barely work on Linux.
I would prefer languages that don't dictate what hardware/software to use for writing them.
The over-engineering in the Java ecosystem has wasted more of my time than saved it.
That over-engineering is what save us from clunky solutions that are good for hello world applications and HN like posts, but fail when doing deployments across heterogeneous platforms on Fortune 500 IT departments with endless number of external contractors and technology stacks hardly seen elsewhere.
And if I have to pick between managing WebSphere containers and taking care of k8s, I will rather pick WebSphere.
Having worked with Spring for years (and still working with it, unfortunately), I have found exactly the opposite.
It does way too much dynamically, making debugging hard and rendering the type-system almost useless.
Sure, it comes with a lot of libraries for handling a large varieties of tasks, but they all seem to be half-assed, and much of the time I either have to work around their limitations or write something myself anyway.
I really don't see why the same thing couldn't have been achieved by writing a bunch of useful libraries that don't depend on a dependency injection framework (which I also don't find much value in).
Finally, it takes forever to startup, making testing a pain. It even means that JUnit tests are slow.
As such, I'd describe it as a good combination of highly dynamic architecture with lots of manual control. Of course, all of this is enabled with copious amounts of magic, which is usually why people don't like Spring.
I don't think a strong enough argument can be made. I'm sure you CAN write web services in Rust, and that in very specific cases it'll have some benefits over Node, but honestly very few people work in an area like that.
Disclaimer: I've settled on using Go to rewrite an existing application. The original app was written in PHP; nothing wrong with PHP per se, but the existing codebase is a mess and the PHP version is hard to keep up to date because of LTS versions of operating systems + very slow and careful updates at our customers (it's network infrastructure). For me, switching to a compiled language that produces a self-contained executable was a compelling argument. I have to admit that I do kinda pine for something like Java again though.