News for hackers. Stuff that matters.
Re:Async2 – The .NET Runtime Async experiment concludes by DougBTX on Thursday August 22, 2024 @08:56AM (#41319734)
The “inherently” means not by default, i.e., the runtime has to support moving green threads between OS threads itself.
Re:Async2 – The .NET Runtime Async experiment concludes by 01HNNWZ0MV43FF on Thursday August 22, 2024 @09:59AM (#41320354)
That's not how I use "inherent", maybe they should just say "default" then?

But that's like... C is also single threaded by default, what isn't?

Re:Async2 – The .NET Runtime Async experiment concludes by jayd16 on Thursday August 22, 2024 @11:36AM (#41321456)
They will never be transparently/fundamentalally managed by the OS alone. The runtime will need to determine how to juggle green threads across multiple OS threads. In that way, this mapping is not inherent.

It can be designed around but that itself is a runtime design decision and I would not say it's akin to default vs custom.

Re:Async2 – The .NET Runtime Async experiment concludes by recursive on Thursday August 22, 2024 @11:59AM (#41321672)
With respect, it's not particularly relevant how you use "inherent". It's a standard usage. Rather than asking the whole rest of the world to change, you should probably learn the definition.
Re:Async2 – The .NET Runtime Async experiment concludes by layer8 on Thursday August 22, 2024 @12:14PM (#41321820)
“Inherently” means “intrinsically”, meaning it’s a characteristic that can’t be changed without changing the nature of the thing. It doesn’t mean “by default”.
Re:Async2 – The .NET Runtime Async experiment concludes by cube2222 on Thursday August 22, 2024 @08:59AM (#41319761)
Ah, that makes sense, thanks!