3 ms·
I think it is really important development in Java space. One reason I plan to use it soon is because it does not bring in complex programing model of "reactive
by geodel 4y ago
I think it is really important development in Java space. One reason I plan to use it soon is because it does not bring in complex programing model of "reactive world" and hence dependency on tons of reactive libraries.
I tried moving plain old Tomcat based service to scalable netty based reactive stack but it turned out to be too much work and an alien programing model. With Loom/Virtual thread, the only thing I will be looking for server supporting Virtual threads natively. Helidon Nima would fit the bill here as all other frameworks/app servers have so far just slapping virtual threads on their thread pool based system. And unsurprisingly it is not leading to great perf expected from Virtual thread based system.
- RcouF1uZ4gsC 4y ago> How long until OS vendors introduce abstractions to make this easier? Why aren't there OS-native green threads, or at the very least user-space scheduling affordances for runtimes that want to implement them without overhead in calling blocking code? Windows had has Fibers[0] for decades (IIRC since 1996 with Windows NT 4.0) 0. https://learn.microsoft.com/en-us/windows/win32/procthread/fibers https://learn.microsoft.com/en-us/windows/win32/procthread/f...
- gpderetta 4y agoFibers are just one part of it. You also need a scheduler and a way to hook into existing blocking APIs.