[sonicgear1]

Java is just a painful language. At that level of abstraction you would expect to work purely on business logic, yet Java makes you just focus on the boilerplate and lacks completely basic features such as tuples, real generics, async/await, anonymous types and more. Spring is another huge pain point, it's slow and verbose in comparison to Go or even .NET. Java is not even close to Kotlin, that's why it was invented in the first place, to not make you want to shoot yourself in the head. Needless to say, I don't see any real use of Java in 2022 and beyond.

[kaba0]

So decide, if you want to work on business logic, why do you want to further dig your grave with async/await, which is by definition an implementation detail?

Also, sprint is not slow at all, especially that servers are very famously IO-heavy. Nonetheless, you can expect better performance for these with project loom.

[BenoitP]

> lacks [...] async/await

I'll take that a a major plus. Sometimes things are improved by what is taken away.

> I don't see any real use of Java in 2022 and beyond.

Well, you see what you see; and the cloud infrastructures sees what it sees.