What happens when one has 10 different ways of handling async IO? Massive ecosystem fragmentation. Ruby has EventMachine, the standard lib, and Celluloid. None

What happens when one has 10 different ways of handling async IO? Massive ecosystem fragmentation. Ruby has EventMachine, the standard lib, and Celluloid. None of these are interoperable. Python has the standard lib, Twisted, and a number of other projects. All have the same problems. C++ has Boost, Asio, a few others. This is more along the lines of where Rust is headed. C has /countless/ options. None of them are standard, and it's totally understood in such an old language. --- Go has goroutines: it's a harmonious, unified ecosystem. I greatly dislike go, but this is one thing they do absolutely correctly. Erlang has fully-preemptive multitasking (which the entire ecosystem is built upon). Haskell has incredible parallelization and concurrency primitives built right into the stdlib. Certain things belong in the stdlib. Async IO is definitely one of them. If not an implementation, a defined, common interface of some nature, to help prevent some of the fragmentation. async/await, if I am not mistaken, will require compiler and borrow-checker support. This would be a good start.