aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--_posts/2020-09-28-crowbar-1-defining-a-c-replacement.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2020-09-28-crowbar-1-defining-a-c-replacement.md b/_posts/2020-09-28-crowbar-1-defining-a-c-replacement.md
index f7be6a1..4e15b1d 100644
--- a/_posts/2020-09-28-crowbar-1-defining-a-c-replacement.md
+++ b/_posts/2020-09-28-crowbar-1-defining-a-c-replacement.md
@@ -3,7 +3,7 @@ title: "Crowbar: Defining a good C replacement"
---
I like Rust a lot.
-That said, the always-opinionated, ~~often-correct~~ [occasionally-correct](https://cmpwn.com/@sir/104946211496582150) Drew DeVault raises some good points in his blog post [Rust is not a good C replacement](https://drewdevault.com/2019/03/25/Rust-is-not-a-good-C-replacement.html).
+That said, the always-opinionated, ~~often-correct~~ [occasionally-correct](https://web.archive.org/web/20201020022457if_/https://cmpwn.com/@sir/104946211496582150) Drew DeVault raises some good points in his blog post [Rust is not a good C replacement](https://drewdevault.com/2019/03/25/Rust-is-not-a-good-C-replacement.html).
He names some attributes that C has and Rust lacks which he thinks are required in a good C replacement.
So what can we say are some features of a hypothetical good C replacement?