That article assumes that there needed to be language level support for asynchronous programming, beyond non-blocking operations.

My point is that that is not true.

If you want to use the blocking paradigms for asynchronous programming, then yes, there does need to be some magic added to make it work.

If, however, you are comfortable with asynchronous programming (and it is not hard) then all you need are the non-blocking operations.

Its massive adoption proves you wrong. You’re welcome to use epoll/kqueue manually if you want. Doesnt mean there’s no need for the ecosystem.

> Its massive adoption proves you wrong

No!

* Window NT in 1991. Displaced much better systems, on mass

* Node.js (my job) is simply dreadful. Mass adoption there too

* It took until 2015 to get half way to a replacement for C for real time systems. C is incredibly prone to failure - and it still has mass adoption. (Very tricky that one)

Popularity is a very bad metric for choosing computer systems.

(Unless you are looking for a job - see above for Node.js)