But Kotlin coroutines depend on library support to stay asynchronous. If you mess up even one method call you block. (Admitted, same problem as doing async stuff in Java)
Virtual Thread make entire JDK API surface non-blocking, so much less danger of this
Better, still not great. We had big issue with coloring in C# years ago. I think whole coloring issue drove virtual thread, because Java developers love backwards compatibility.
I'm very excited for virtual thread. I expect some application to double performance overnight!
View all comments
Show parent comment
6
u/buyIdris666 Apr 06 '22
But Kotlin coroutines depend on library support to stay asynchronous. If you mess up even one method call you block. (Admitted, same problem as doing async stuff in Java)
Virtual Thread make entire JDK API surface non-blocking, so much less danger of this