

Can you talk a bit about that project for us please?

Ron Pressler: Hello and thank you for having me.Ĭharles Humble: I first came across your work around about 2016 via project Quasar, which was trying to add fibers or lightweight threads to Java using bytecode manipulation tricks and was something of a forerunner to Loom.

This week, I'm joined by Ron Pressler, who is the technical lead for Project Loom at Oracle. I am a freelance technology consultant and communicator, managing editor for cloud native consultancy firm Container Solutions and a co-host of this show. In the future (post the first GA release), the team may look at adding explicit tail-call optimisation.Ĭharles Humble: Hello, and welcome to the InfoQ Podcast.
#We haf to give the answers in semaphor how to
Debugging is still challenging and the project Loom team is working with the various IDE vendors on how to present large numbers of threads.There aren't any new APIs you have to learn, but you do need to unlearn many habits such as using thread pools to deal with resource contention. Virtual threads are cheap enough to have a single thread per task, and eliminate many of the common issues with writing concurrent code in Java.Project Loom is supposed to break that dilemma through virtual threads. Currently Java developers are faced with a choice between writing code that's harmonious with the design of the platform but is not scalable, or writing code that makes efficient use of existing hardware with asynchronous programming and fighting the platform.In OpenJDK, Java threads are just thin wrappers around OS threads and OS threads are a very precious resource a modern OS can't support more than a few thousand active threads at a time.
