This is perhaps why the comment added "Just like Martin Odersky intended it to be!"

There are just too many ways to use Scala, and everyone thinks they're doing it "idiomatically".

Pattern matching with only positional destructuring is a bad feature. I've written enough Scala to say this with confidence.

>> state of the art GCs

> That just isn't true

Generational ZGC is free for everyone to use.

>> Preemptive scheduling plus M:N mapping

AFAIK, in the current implementation, Java's virtual threads yields only when they block (cooperative). But the spec allows a JVM to implement them as preemptive.

Well, they do only yield on block and whatnot, but that's very much different from adding manual async/await keywords, I would say.

Kotlin's coroutines basically had the same API as Go's. But also the ability to confine some coroutines' execution into certain threads (e.g. UI main thread).

Then they added structured concurrency, which roughly solves the same problem as Go's context, arguably more elegantly.

Kotlins coroutines are super super super underrated imo. I loved working with them so much before ai. Fuck ai.

Sorry my ignorance, but what does AI have to do with you not being able to use kotlins concurrency model?

Ai makes it not worth hand crafting source code anymore imo

I said it before and I’ll say it again - kotlin is the most fun programming language.

This might be the your missing puzzle piece:

https://en.wikipedia.org/wiki/Committee_to_End_Pay_Toilets_i...

You are of course right about what the word "commons" refers to. Still, I want to quibble.

Maybe the definition covers both, but I still think it's worth distinguishing between incentives creating a bad equilibrium and simply antisocial behaviours. When I hear "tragedy of the commons", I think of the former.