I wrote a #rust2020 blog post https://www.ultrasaurus.com/2019/12/rust-2020/ … -- perspectives from a few months learning @rustlang
-
-
Replying to @ultrasaurus @rustlang
URL parsing in the standard library is a bad idea. How do you then react fast enough to changes in the specification? How do you introduce breaking changes? Which standard do you implement? The vague underspecified RFCs or the WHATWG Living Standard?
1 reply 0 retweets 4 likes -
The URL standard changes very infrequently in backward-compatible ways, and variants can be addressed with flags — the key point is to converge on well-vetted parsing code with consistent semantics for same behavior....
2 replies 0 retweets 0 likes -
Safe code is more than memory safety
1 reply 0 retweets 0 likes -
My key point is that parsing input is risky and not actually very interesting, easy to make mistakes....
1 reply 0 retweets 0 likes -
As long as engineers have to do a detailed review of multiple crates before they add URL parsing to their app/library, then Rust isn’t mature enough to deliver on its promises (which is ok, if that’s where u are at)
2 replies 0 retweets 0 likes -
Engineers who think URL parsing is easy haven’t been writing Internet software very long or don’t care about security / privacy ...
2 replies 0 retweets 0 likes -
Something that is straightforward and boring to implement can still be difficult to implement correctly and can be challenging to verify correctness
1 reply 0 retweets 0 likes
Rust standard library maintainer here; I would encourage you not to see the standard library as the solution to these points. If I were picking a url lib, I would trust the one used by a real browser with a billion real users written by browser experts, over the one in std lib.
-
-
For the record, I've updated my blog post on
#Rust2020 and safety being not just about memory safety and concurrency. The primary point was not about a change to the std lib. https://www.ultrasaurus.com/2019/12/rust-2020/ …1 reply 0 retweets 0 likes - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.