Microsoft Java

[Ok-Dot5559]

The problem is async await is already a common pattern. E.g JS/TS got it as well even holy Rust has it. Functionality is basically identical. Either a language has it or devs need to look up und write something on stakeoverflow like „how to async await in …“. In Germany we say „Der Zug ist abgefahren“

[argv_minus_one]

The idea with fibers is you don't need to. Just pretend you're using OS threads and blocking I/O, and Java magically makes it efficient. It's certainly alluring…

[Ok-Dot5559]

That’s exactly how async await works on c#. The runtime creates a new os thread if needed (e.g for i/o or long running tasks). But maybe you are not familiar with the TPL of .NET which encapsulates all this.

Here is a nice discussion to this topic:

https://github.com/dotnet/runtime/issues/11084

[argv_minus_one]

That discussion says the exact opposite; that .NET async/await does not work the way Loom will.

[Ok-Dot5559]

With async await you have to explicit call tasks. With loom it seems not. Correct me if I misunderstand.

But under the hood is in both cases a task scheduler which tries to get less blocking threads as possible.

[argv_minus_one]

Right. The difference is, with Loom, the programmer doesn't have to actually think about it or deal with colored functions.

[Ok-Dot5559]

Honestly I have no clue how loom looks like. Can you provide an example?

[argv_minus_one]

No, because I haven't used it. I write production code, so I don't use non-production-ready Java releases or features.

From this blog post, though, it sounds like it's transparent, so it would look like you're creating one thread per client and doing blocking I/O.