3 ms·
Loom and Valhalla both seem to be very powerful new features for the JVM that seem to take forever to land. Valhalla was first announced in 2014, and Loom in 2
by the_duke 5y ago
Loom and Valhalla both seem to be very powerful new features for the JVM that seem to take forever to land.
Valhalla was first announced in 2014, and Loom in 2017.
Does anyone have some insight on when either of these might finally be ready?
For those not familiar:
Valhalla: introduces "inline types" (structs) and allows using primitive types as generics. Has the potential for quite significant performance improvements because it can reduces all the pointer chasing currently required.
Loom: allows Java to work like Go: code that looks single-threaded but where IO is actually driven by a runtime on a hand full of threads. As in: async without the development and debugging complexity.
- pjmlp 5y agoLook like this, it took 10 years to get modules into C++, which only VC++ from about 10 compilers, properly supports, only a subset of concepts managed to get in after 10 years, co-rountines are only at language level, everything executors and networking might only land on C++26. So I am not concerned that engineering efforts that allow .jar files from 2000 to keep running in Valhalla/Loom aware JVMs (minus modules issues) to also take equally amount of time.
- ta988 5y agoYes it seems that anything that takes more than the average tenure in a tech company is defined as "forever" now.
- debug-desperado 5y agoI'd wager they will both be ready before Go gets generics.