3 ms·
A few years back I started using Rust after spending many years working with Go full-time and the first thing I noticed was that the team really focused on only
by mtalantikite 7y ago
A few years back I started using Rust after spending many years working with Go full-time and the first thing I noticed was that the team really focused on only providing the language, that libraries like HTTP were being pushed out to the community to contribute. It's a totally fair position for a language to take, but I found it disappointing coming from Go where I knew I could just use 'net/http' and move on to solving problems.
This is the first I've heard of this conflict in the Rust community, but honestly it's not at all surprising. People write lots of web servers and if you're relying on your community to provide critical libraries (http is pretty critical in 2020) things like this are bound to happen. I really wish Rust core could provide a standard library of tools more akin to Go as I really enjoyed working with it when I was learning it.
- steveklabnik 7y agoThe language team has been focusing on providing the primitives needed for an efficient HTTP client and server, that is, async/await. That only got stabilized a few weeks ago. If we had put HTTP in the standard library before then, it would have only been synchronous. That would have been a huge drawback.
- mtalantikite 7y agoOh absolutely, you actually mentioned that to me a few years back when I was first looking at Rust, and that’s a totally reasonable place to have been in. It’s just unfortunate that so many people decided to depend on an external library/framework and then got upset like this. For me it meant Rust wasn’t a language I should use for web servers at that moment, which hopefully won’t be the case for too much longer. I will say that as a user it’d be great to see an officially maintained lib like ‘net/http’, even if it isn’t a part of the std lib itself.