3 ms·
As opposed to what platform? Also, they did that in a completely backwards compatible way, so that programs that were written before Go was even a thing will a
by kaba0 4y ago
As opposed to what platform?
Also, they did that in a completely backwards compatible way, so that programs that were written before Go was even a thing will also benefit, so if you will, Java has out of the doors orders of more “goroutine”-aware code as is, than Go will likely ever will.
- bheadmaster 4y ago> As opposed to what platform? Go. > programs that were written before Go was even a thing will also benefit As far as I understand virtual threads, they have a new API for creating them, so older programs will at the very least need some source change and a recompilation in order to use them. Of course, if there's a JVM flag to automatically use virtual threads in place of OS threads, please correct me :) > Java has out of the doors orders of more “goroutine”-aware code as is, than Go will likely ever will. I honestly doubt that older code is "goroutine"-aware, as virtual threads are used in a different way than ordinary OS threads. I don't think there's any code that spawned hundreds of thousands of OS threads before, which would be the main benefit of using virtual threads.