commit: 56047076f3776a5e2f6f6a55d4e5627d7d3d78fd
parent 00d937dc7fb331806e0df479253f11d35b762a40
Author: Drew DeVault <sir@cmpwn.com>
Date: Tue, 9 Feb 2021 10:13:51 -0500
Fix typo
Diffstat:
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/content/blog/Rust-move-fast-and-break-things.gmi b/content/blog/Rust-move-fast-and-break-things.gmi
@@ -2,7 +2,7 @@ Rust breaks a lot of stuff, and in ways that are difficult to fix. This can have
=> https://doc.rust-lang.org/nightly/rustc/platform-support.html Rust: Platform support
-The Rust cargo cult needs to pause and re-evaluate. Switching to Rust breaks things for anyone who steps even a toe out of the norm of Linux/macOS/Windows on x86_64 or aarch64. Even on the supported platforms it comes with a substantial burden on build requirements, calling for 10× to 100× or more RAM, CPU time, and power usage. Whatever its benefits, choosing Rust is ultimately choosing to lock a large group people out of your project, and dooming many more to struggle and frustration. These are real trade-offs that you need to seriously consider.
+The Rust cargo cult needs to pause and re-evaluate. Switching to Rust breaks things for anyone who steps even a toe out of the norm of Linux/macOS/Windows on x86_64 or aarch64. Even on the supported platforms it comes with a substantial burden on build requirements, calling for 10× to 100× or more RAM, CPU time, and power usage. Whatever its benefits, choosing Rust is ultimately choosing to lock a large group of people out of your project, and dooming many more to struggle and frustration. These are real trade-offs that you need to seriously consider.
Rewrite-it-in-Rust has become a moral imperative. Well, here’s a moral argument: throwing away serviceable computers every couple of years to upgrade is a privilege that not all of your users have, contributes to climate change, and fills up landfills. As far as security is concerned, some matters demand leaving the norm: old hardware is the only kind that can avoid proprietary firmware blobs, Intel ME or AMD PSP, and UEFI. Novel hardware which addresses issues like microcode and open hardware, like POWER9 and RISC-V, are also suffering under Rust’s mainstream-or-bust regime. Anyone left behind is forced to use the legacy C codebase you’ve abandoned, which is much worse for their security than the hypothetical bugs you’re trying to save them from.
diff --git a/content/blog/Rust-move-fast-and-break-things.md b/content/blog/Rust-move-fast-and-break-things.md
@@ -24,8 +24,9 @@ anyone who steps even a toe out of the norm of Linux/macOS/Windows on x86_64 or
aarch64. Even on the supported platforms it comes with a substantial burden on
build requirements, calling for 10× to 100× or more RAM, CPU time,
and power usage. Whatever its benefits, choosing Rust is ultimately choosing to
-lock a large group people out of your project, and dooming many more to struggle
-and frustration. These are real trade-offs that you need to seriously consider.
+lock a large group of people out of your project, and dooming many more to
+struggle and frustration. These are real trade-offs that you need to seriously
+consider.
Rewrite-it-in-Rust has become a moral imperative. Well, here's a moral argument:
throwing away serviceable computers every couple of years to upgrade is a
