> Hardly, how to get the benefits of "structured concurrency" with it: > <https://openjdk.org/jeps/428>
I wouldn't pretend to know why one excludes the other. What I do know is that at this point Java has at least 3 concurrency models: Original heavy threats New virtual threats And parallel streams But Java is a managed language running on a huge powerful VM, same goes for Erlang. We're hardly in Nim territory here... And I know it would suit Nim to have a simple, intuitive and elegant threading api at its core. Anything more elaborate could be third party. - But hey that's just me being reasonable...
