(Replying to PARENT post)

I think the biggest impact of virtual threads is that the ecosystem will abandon asynchronous APIs. No more futures, callbacks, servers where you have to make sure not to block the thread, reactive frameworks, etc. Just nice simple imperative blocking code. Nima is the first example i've seen:

https://helidon.io/nima

We've had two production bugs in the last two weeks caused by handlers blocking the server thread in apps using an async web framework, which would simply not have happened with a synchronous server.

๐Ÿ‘คtwic๐Ÿ•‘2y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

You'll still have the structured concurrency calls but that's much better than pure callback hell.
๐Ÿ‘คjayd16๐Ÿ•‘2y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

They won't abandon async callback based code.

VT have too much memory overhead to be equivalent.

๐Ÿ‘คwinrid๐Ÿ•‘2y๐Ÿ”ผ0๐Ÿ—จ๏ธ0