Erjang exists, but it seems pretty dormant. JVM and BEAM have pretty different philosophies, so while you could probably add messaging and distribution to JVM, I don't think it would be the same. I think it would be hard to get one thread-like thing per connection and millions of connections per OS process to work on the JVM, unless you can get OS threads to scale that high (which seems unlikely?).
Yeah, that might do it, although from a brief skim, I suspect it's likely to end up with function color issues making it hard to really embrace virtual threads. Interesting to read about, thanks.
No - they are doing the opposite. A "lite" thread will be a thread, period. It has a different implementation, but it behaves the same way. You ask for one or the other, but they basically work the same way from the PoV of the programmer.
Project Loom is the only approach that truly promises to solve function colouring, user code just uses the thread API, while the underlying implementation can be swapped out transparently. I'm not aware of any other ones that do this (not, not even Zig).
