An airhacks.fm conversation with Nicolai Parlog (@nipafx) about:
JavaOne is back,
virtual threads and Java 19,
the old Java’s green threads,
mapping between OS threads and green threads cannot be changed after assignment,
Project’s Loom virtual threads are not assigned to a core,
virtual threads could become the default,
the artificial use of reactive programming,
Project Loom performs as good as reactive, but may consume more memory,
operational costs vs. developer costs,
structured concurrency in looom,
millions of threads in no time,
the memory overhead depends on the call stack,
structured programming is as powerful as go to,
structured programming and structograms,
structured concurrency,
a structured task scope in try with resources,
creating all tasks in one scope,
StructuredTaskScope has to be a part of Java,
StructuredTaskScope maintains the virtual thread hierarchy - the parent,
structured concurrency and EJBs,
structured concurrency and transactions,
CompletableFuture and StructuredTaskScope,
StructuredTaskScope and shutdown on success or shutdown on failure,
Boundary Control Entity and structured concurrency,
Project Loom Brings Structured Concurrency video on java inside,
project Helidon and virtual threads,
the premature optimisation of Loom,,
the sun misc Unsafe,
the great inside.java portal,
Nicolai Parlog on twitter: @nipafx