Hacker News Reader

What's wrong with Rust's networking support? I actively wouldn't want it in the standard library, because you'll almost certainly end up stabilising something suboptimal. And then your stuck with it. Its not like it's hard to use 3rd party libraries in Rust. Its literally a case of adding one line to your Cargo.toml file.

View on HN

I agree that with the rapid change in the language, it's probably premature to standardize on one API for networking. But as a newcomer to Rust, it's really overwhelming when there are like 5 different async websocket libraries, none of which is a clear standard in the community, each with relatively sparse documentation (other than the method signatures/impls).

Also, I haven't been following the Go ecosystem lately, so I could be wrong, but they seem to have done a good job at creating standard libraries for common stuff like http serving, and those libraries seem to have aged just fine.

Reply on news.ycombinator.com