Re:Four Years of Rust
by pcwalton on Wednesday May 15, 2019 @01:19PM
(#19921629)
Well, async I/O is important to get early. Otherwise we're going to have an entire ecosystem of synchronous networking code, and there's no going back from that. You can look at languages like Ruby for what happens if you don't get an async I/O story before the package ecosystem develops.
[ Parent
| on HN ]
Java seems to have done pretty well, and it didn't have broad stdlib support for asynchronous I/O until a few years ago.
NIO was introduced in Java 1.3.
That's non blocking, not async as in the async that rust is developing.