improve wording + FAQ

sylvestre · sylvestre · commit 906eda4e74cb · 2024-03-26T23:45:20.000+01:00
diff --git a/content/blog/2024-02-extending.md b/content/blog/2024-02-extending.md
@@ -1,16 +1,16 @@
 +++
-title = "Extending the coreutils project - Rewriting base tools in Rust "
+title = "Extending the Coreutils project - Rewriting base tools in Rust "
 draft = true
 date = 2024-03-26
 authors = ["Sylvestre Ledru", "Terts Diepraam"]
 +++
 
-Over the last 4 years, we have been working at reimplementing some of the key linux tools in Rust. We started with the [Coreutils](https://github.com/uutils/coreutils) and [findutils](https://github.com/uutils/findutils).
+Over the last 4 years, we have been working at reimplementing some of the key Linux tools in Rust. We started with the [Coreutils](https://github.com/uutils/coreutils) and [findutils](https://github.com/uutils/findutils).
 
 As we approach feature parity with the GNU Coreutils implementation, and as its adoption in production environments continues to expand, we have been thinking about what is next.
 
-Given the overwhelming positive feedback around this initiative, we are going to extend our efforts to rewrite other part of the modern Linux/Unix/Mac stack in Rust (still with Windows support in mind when relevant).
-We also noticed a lot of contributions on these projects coming for a lot of different hackers (475 different contributors on Coreutils!).
+Given the overwhelming positive feedback around this initiative, we are going to extend our efforts to rewrite other parts of the modern Linux/Unix/Mac stack in Rust (still with Windows support in mind when relevant).
+We also noticed a lot of contributions on these projects coming from a lot of different hackers (475 different contributors on Coreutils!).
 With the growing enthusiasm for Rust and the eagerness to learn it, now is the best time to push this project. We think that rewriting in Rust will help with the longer term maintenance of the ecosystem, ensuring it stays robust, safe and welcoming for new generations of contributors.
 
 We are
@@ -26,11 +26,11 @@ For now, we are going to focus on:
 * [util-linux](https://github.com/uutils/util-linux) - [Good first issues](https://github.com/uutils/util-linux/labels/good%20first%20issue)
   A couple programs started
 * [bsdutils](https://github.com/uutils/bsdutils) - [Good first issues](https://github.com/uutils/bsdutils/labels/good%20first%20issue)
-  One program start
+  One program started
 * [login](https://github.com/uutils/login/) - [Good first issues](https://github.com/uutils/login/labels/good%20first%20issue)
   Just the skeleton
 * [hostname](https://github.com/uutils/hostname/) - [Good first issues](https://github.com/uutils/hostname/labels/good%20first%20issue)
-  almost empty
+  Almost empty
 
 
 These packages are part of the essential list on Debian & Ubuntu.
@@ -56,4 +56,16 @@ For consistency purposes and not interested by a license debate, we are going to
 The binaries are too big?
 -------------------------
 
-Does it really matter? Yes, Rust binaries are usually bigger then GNU but we don't think it is a blocker, even for embedded devices.
+Does it really matter? Yes, Rust binaries are usually bigger than GNU but we don't think it is a blocker, even for embedded devices.
+
+
+Is it really safer?
+-------------------
+
+While Rust is clearly a better language than C/C++ for security, these programs are often very safe. It isn't a key argument for us for
+this rewrite.
+
+What about performances?
+------------------------
+
+Although we haven't entered the optimization phase, Rust's modern design inherently facilitates some straightforward performance improvements.
