New candidate JEP: 425: Virtual Threads (Preview)

[Eric Kolotyluk]

Some comments...


      Improving scalability with the asynchronous style

A term I like to use in this context is "/*reduced cognitive load*/" 
with respect to /*Developer Experience*/ (dX).

While I have become fairly proficient using the 'reactive' 'callback' 
'non-blocking' style of programming, it imposes a higher cognitive load, 
it causes me to worry more that I have made mistakes, because in this 
style I do make more mistakes.

Also, I am tired of Scala snobs telling me I am stupid because I ask 
stupid questions regarding reactive programming. But that's a whole 
other discussion... Don't get my wrong, I love programming in Scala, I 
just don't like Scala snobs... Once Loom is finished, I am sure that 
Scala, Akka, and Kotlin will quickly adopt loom thinking because it's 
just so obviously good... (and they are already talking about it).

However, all the other points in this section are well made, but I feel 
it's increasingly important to call out dX improvements these days where 
I feel reactive style has undermined much of my dX. Reactive style has 
made me a better programmer, but I like the choice Loom gives me.

I will comment more later as I don't want to cover too many topics at 
once...

Cheers, Eric

On 2022-04-06 9:10 a.m., mark.reinhold at oracle.com wrote:
> https://openjdk.java.net/jeps/425
>
>    Summary: Introduce virtual threads to the Java Platform. Virtual
>    threads are lightweight threads that dramatically reduce the effort
>    of writing, maintaining, and observing high-throughput concurrent
>    applications. This is a preview API.
>
> - Mark