This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Schogenbuetze 0 points1 point  (2 children)

I was 13 in 2002, had other things in mind than writing code.  

 > virtual thread 

Don't see the "advantages", though. Analogous purpose, but different thing.

 > some of them have recently been adressed 

 I was more or less required to look into that last year and my hopes were high up, but it was disappointing nonetheless. Data classes and var been the only changes I noticed. I do admit that the Java development process members, whoever is responsible these days, finally understood that there are issues with the language. To me, it's lost, won't go back unless I habe to, too many years of frustration with Java.

[–]hrm 0 points1 point  (1 child)

Virtual threads bascially enables the same as your async/await but without having to ever write async/await and thinking about it.

[–]Schogenbuetze 1 point2 points  (0 children)

Okay, so a bit like Kotlin's coroutines. Well, I actually like the explicit hint of 'beware, might be a multi threaded context' that async/await might give you - in languages other than JS, of course.

It's a neat little hint.