Asynchronous IO: the next billion-dollar mistake?

&gt; More specifically, what if instead of spending 20 years developing various approaches to dealing with asynchronous IO (e.g. async&#x2F;await), we had instead spent that time making OS threads more efficient, such that one wouldn&#x27;t need asynchronous IO in the first place?<p>1) Moore&#x27;s law for single cores has been over for a while 2) We are necessarily in a distributed world 3) Amdahl&#x27;s law still applies 4) Concurrent operations would still be needed.

Linux has already optimized threads extensively; AFAIK the overhead is mostly in the CPU at this point (fortunately Intel&#x2F;AMD continue to reduce system call and context switch overhead).<p>Using raw threads also has its own footguns but fortunately we have libraries like j.u.c and TBB to provide safer abstractions over threads. Unfortunately these libraries matured after async so most programmers aren&#x27;t familiar with concepts like fork&#x2F;join.