News for hackers. Stuff that matters.
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.
Re:Four Years of Rust by zbentley on Thursday May 16, 2019 @12:06AM (#19926051)
Java seems to have done pretty well, and it didn't have broad stdlib support for asynchronous I/O until a few years ago.
Re:Four Years of Rust by pjmlp on Thursday May 16, 2019 @01:01AM (#19926271)
NIO was introduced in Java 1.3.
Re:Four Years of Rust by jnordwick on Thursday May 16, 2019 @01:52AM (#19926497)
That's non blocking, not async as in the async that rust is developing.
Re:Four Years of Rust by pjmlp on Thursday May 16, 2019 @02:36AM (#19926692)
Non blocking code is asynchronous by definition, regardless of the syntax sugar.