3 ms·
The first chapter of the Rust book covers how to integrate dependencies in your workflow. The only thing not covered there is choosing which web framework to us
by steveklabnik 4y ago
The first chapter of the Rust book covers how to integrate dependencies in your workflow. The only thing not covered there is choosing which web framework to use. To do that, you either Google it, ask around, or just pick literally any of them and give it a try.
You’ll notice the sibling comment did the same thing but with a different web framework they prefer. That’s great too. But other than the choice, it’s entirely agnostic. Another sibling even posted a step by step tutorial, if that level of specificity is helpful.
- yazaddaruvala 4y agoYou're right that adding dependencies is easy, but you're significantly downplaying the discoverability of quality crates for specific usecases. When people say "we need a rich standard lib" they are more interested in a "blessed set of crates" than a "it should be pre-downloaded with the compiler".
- steveklabnik 4y agoI mean I think my answer is the best anyone can do. It’s not as if there’s never packages competing with the standard library, and finding one you like and then always use is a one-time cost. There’s a ton of ways to find the answer to this question easily. It is of course true that you have to look. While two different ones were mentioned in this thread even, a new user would be easily served by either.