I don't think .NET has virtual threads (async/await doesn't count), and it definitely doesn't have anything similar to ZGC/Shenandoah — two garbage collectors that provide sub-millisecond pauses with heaps up to the multiple terabyte range. You can also go completely pause-less on commercial JVMs from Azul.

It's not generational GC, it's generational ZGC.

ZGC is a concurrent GC, both the marking phase and the evacuation phase are done concurrently with the program running. A generational ZGC is a generational concurrent GC.

MS does not have such kind of tech.

Well, yeah, that's been Java's explicit philosophy for decades. Let other languages evaluate cool new features first, then learn from their mistakes and promise backward compatibility "forever".

Linux support is bad on MS tech. Poor ecosystem and VM isn’t that great. JVM with ZGC is fast on Linux. Biggest lack is Value Types.

And I’m not deploying to Windows. That’s right out.

But lots of people find it useful, so more power to them. For me, it must deploy on Linux. That’s a dealbreaker. It’s not enough if some bare functionality is on Linux. I don’t want to be experiencing the equivalent trouble of trying to have a musl-only build.

JNI story is great. Can bind easily with rust-jni on Linux.

But need value types and some longer primitives (i128 and u128 would be nice).

Aren't you quite limited when targeting or developing on non-Windows platforms with .NET?

Okay sure let's just ignore Linux, Apple Silicon, BSD support by .NET and Visual Studio.

It's obviously "MS tech is boring", e.g. TypeScript and VSCode.