logo

drewdevault.com

[mirror] blog and personal website of Drew DeVault git clone https://hacktivis.me/git/mirror/drewdevault.com.git
commit: b1d572dbc1e5f25ac36b0d8c8c571697a4ffc28b
parent 56047076f3776a5e2f6f6a55d4e5627d7d3d78fd
Author: Drew DeVault <sir@cmpwn.com>
Date:   Tue,  9 Feb 2021 10:14:44 -0500

Fix typo 2

Diffstat:

Mcontent/blog/Rust-move-fast-and-break-things.gmi2+-
Mcontent/blog/Rust-move-fast-and-break-things.md2+-
2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/blog/Rust-move-fast-and-break-things.gmi b/content/blog/Rust-move-fast-and-break-things.gmi @@ -11,7 +11,7 @@ C is not memory safe. It suffers from undefined behavior. These are valid compla => https://sel4.systems/ seL4 => https://www.redox-os.org/ RedoxOS -A working C toolchain (say, cproc and qbe) can be written in a couple tens of thousands of of code. The only working Rust toolchain is tens of millions of lines of C++ and Rust code. How many undiscovered bugs do you think these two toolchains have when compared? How many of those are security issues? How much relative work would it be to debug them, or port them to new — or old — platforms? How often do these respective codebases churn, creating a larger maintenance burden and introducing new bugs/vulnerabilities? I can bootstrap a working C toolchain in about 10 minutes. I spent a week trying to do that for Rust, and failed. That matters. +A working C toolchain (say, cproc and qbe) can be written in a couple tens of thousands of lines of code. The only working Rust toolchain is tens of millions of lines of C++ and Rust code. How many undiscovered bugs do you think these two toolchains have when compared? How many of those are security issues? How much relative work would it be to debug them, or port them to new — or old — platforms? How often do these respective codebases churn, creating a larger maintenance burden and introducing new bugs/vulnerabilities? I can bootstrap a working C toolchain in about 10 minutes. I spent a week trying to do that for Rust, and failed. That matters. => cproc https://sr.ht/~mcf/cproc/ => qbe https://c9x.me/compile/ diff --git a/content/blog/Rust-move-fast-and-break-things.md b/content/blog/Rust-move-fast-and-break-things.md @@ -52,7 +52,7 @@ continuous maintenance, that number will only shrink. [2]: https://www.redox-os.org/ A working C toolchain (say, [cproc][3] and [qbe][4]) can be written in a couple -tens of thousands of of code. The only working Rust toolchain is tens of +tens of thousands of lines of code. The only working Rust toolchain is tens of millions of lines of C++ and Rust code. How many undiscovered bugs do you think these two toolchains have when compared? How many of those are security issues? How much relative work would it be to debug them, or port them to new &mdash; or