add story for picking a web server #127
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nikomatsakis
requested changes
Apr 6, 2021
There was a problem hiding this comment.
This is great, thanks. I left one nit -- I feel like one of the morals may be overly kind in claiming that Rust is "ready for the web". I feel like the story is showing all the ways Rust is not ready. Maybe we can even just delete that part of the moral and focus on the "confusing" part?
|
|
||
| ### **What are the morals of the story?** | ||
| * Rust's ecosystem is ready for the web. There are a ton of brilliant libraries and frameworks out there. But web developers that are new to Rust may struggle with the idea that before picking a web server, they have to pick an async runtime. | ||
| * In a typical web server project, dependencies that use async features form an intricate web which is hard to decipher for both new and seasoned Rust developers. Alan picked Tide and reqwest, only to realise later that they are not compatible. How many more situations like this will he face? Can Alan be confident that it won't happen again? |
There was a problem hiding this comment.
I guess my rephrasing overlaps with this.
There was a problem hiding this comment.
not sure I follow. Do you mean getting rid of the first point altogether?
There was a problem hiding this comment.
I think I would combine them. For example:
- Rust's ecosystem has a lot of great components that may individually be ready for the web, but combining them is still a fraught proposition. In a typical web server project, dependencies that use async features form an intricate web which is hard to decipher for both new and seasoned Rust developers. Alan picked Tide and reqwest, only to realise later that they are not compatible. How many more situations like this will he face? Can Alan be confident that it won't happen again? New users especially are not accustomed to having to think about what "runtime" they are using, since there is usually not a choice in the matter.
Co-authored-by: Niko Matsakis <[email protected]>
rylev
reviewed
Apr 7, 2021
eminence
reviewed
Apr 7, 2021
| * Rust's ecosystem has a lot of great components that may individually be ready for the web, but combining them is still a fraught proposition. It can also be confusing to web developers that are new to Rust, who may struggle with the idea that before picking a web server, they have to pick an async runtime. | ||
| * In a typical web server project, dependencies that use async features form an intricate web which is hard to decipher for both new and seasoned Rust developers. Alan picked Tide and reqwest, only to realise later that they are not compatible. How many more situations like this will he face? Can Alan be confident that it won't happen again? | ||
| * The situation is so complex that it's not enough knowing that all dependencies use the same runtime. They all have to actually be compatible with the same runtime **and** version. Newer versions of reqwest are incompatible with the latest stable version of actix web (verified at the time of writing) | ||
| * Developers that need a stable environment may be fearful of the complexity that comes with managing async dependencies in Rust. For example, if reqwest had a security or bug fix in one of the latest versions that's not backported to older ones, Alan would not be able to upgrade because actix web is holding him back. He has in fact to wait until **ALL** dependencies are using the same runtime to apply fixes and upgrades. |
There was a problem hiding this comment.
I like this point. I'm not sure any of the other stories mention this aspect so clearly. I'm glad it's mentioned here.
nikomatsakis
requested changes
Apr 8, 2021
Co-authored-by: Niko Matsakis <[email protected]>
|
thanks all for your comments! I've just pushed a couple of commits that I think answer all of them |
rylev
reviewed
Apr 9, 2021
Co-authored-by: Ryan Levick <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is my take on a story following #95 and #112