Hacker News Reader

Comment by sgt | Hacker News Reader

So clearly Rust is ready for tiling window managers. When will Rust be ready for the web (at least to the level of where Go is right now) ?

View on HN

The web ecosystem in Rust is still very early. There have been some awesome efforts recently in pushing a full-featured http library [0] (Hyper is now powering Servo [1]). The web ecosystem can't expand fully without a strong http library and previously, an unmaintained rust-http was used.

The next issue, if we're talking about high-performance http is asynchronous I/O which Rust doesn't currently bundle with (now that Rust has dismantled it's green threading runtime and is now sticking with native threading). However, mio [2], a lower-level Rust library in providing proper I/O abstractions that support async apis and the like is progressing pretty well.

The awesome part about Rust is that you have full control over the system. This allows one to build something like mio even though Rust doesn't support async I/O or a more efficient threading model, etc...

[0]: https://github.com/hyperium/hyper [1]: https://github.com/servo/servo/pull/4198 [2]: https://github.com/carllerche/mio

What makes you think that it isn't already?

Seems it's far from being mature enough to use in production - from a couple of sources including: http://arewewebyet.com/

What is it that makes writing an HTTP client so hard? It seems bizarre that a project like teepee could have been in active development for 8 months or more, and still not be anywhere near usable.

Well, http://github.com/carllerche/curl-rust has been working great for me. Sure, it uses libcurl so it isn't pure Rust, but that doesn't make it not work :-)

Teepee is mainly a HTTP server though - I can imagine that the HTTP client part of the library is more trivial.

Reply on news.ycombinator.com