|author||Daniel Silverstone <email@example.com>||2019-11-25 22:21:57 +0000|
|committer||Daniel Silverstone <firstname.lastname@example.org>||2019-11-25 22:21:57 +0000|
1 files changed, 10 insertions, 4 deletions
diff --git a/posts/rust-2020.mdwn b/posts/rust-2020.mdwn
index 1dbe808..cabd0b6 100644
@@ -19,10 +19,10 @@ with Rust except read blogs and reddit for a year. Then I went and did [Advent
of Code 2017][aoc2017] in Rust and reminded myself of why I enjoyed the
language. This time I decided I'd do more with Rust and started playing
around. I wrote bits and bobs through 2018, but still failed to do anything
-major until once again, December rolled around and I did [Advent of
-Code 2018][aoc2018] in Rust, learning an awful about procedural macros and
-other useful things. This was the time of the 2018 Rust edition which also
-spurred me on to do more useful stuff.
+major until once again, December rolled around and I did [Advent of Code
+2018][aoc2018] in Rust, learning an awful about procedural macros and other
+useful things. This was the time of the 2018 Rust edition which also spurred
+me on to do more useful stuff.
@@ -162,6 +162,12 @@ unimportant or simply ignored. I am very guilty of this myself. I am
responsible for `rustup` and it's quite possibly the most `UNIX`y part of
the Rust ecosystem, and yet is pretty much mandatory for every Windows user.
+Another example of this is the `rust-docs` component which contains tens
+of thousands of small files which causes Windows based anti-virus systems
+significant indigestion. We ended up adding a "minimal" profile to `rustup`
+so that Windows users could skip installing the docs, but that's not great as
+a long-term solution.
As Rust tries to get included into more companies, this friction is going to be
more and more important to resolve. A huge number of companies expect their
developers to use Windows desktops, even when they're working on Linux hosted