Improve wording

Improve wording for intelligibility.
This commit is contained in:
finga 2021-09-06 14:07:21 +02:00
parent 9ced692aa8
commit 1db227f540

View file

@ -36,7 +36,7 @@
*** Rust, the language
- A bit more than 10 years old (2010)
- Memory safe without gcing, optional ref counting
- Memory safe without gcing, optional reference counting
- Ownership, lifetimes, traits, functional paradigms
- Variables are immutable by default and can be shadowed
- Performance of idiomatic Rust is comparable to the performance
@ -44,7 +44,7 @@
- A well designed language and ecosystem
** Strengths and Weaknesses[fn:2]
*** Things Rust does measurably really well
*** Things Rust does measurably really well (Strengths)
- Compiled code [[https://benchmarksgame-team.pages.debian.net/benchmarksgame/which-programs-are-fastest.html][about same performance as C / C++]], and excellent
[[https://dl.acm.org/doi/10.1145/3136014.3136031][memory and energy efficiency]].
- Can [[https://www.chromium.org/Home/chromium-security/memory-safety][avoid 70% of all safety issues]] present in C / C++, and most
@ -55,10 +55,10 @@
LLVM).[fn:3]
- [[https://insights.stackoverflow.com/survey/2021#technology-most-loved-dreaded-and-wanted]["Most loved language"]] for 6 years in a row.
- Modern tooling: ~cargo~ (builds just work), ~clippy~ (450+ code
quality lints), ~rustup~ (easy toolchain mgmt).
quality lints), ~rustup~ (easy toolchain management).
** Strengths and Weaknesses[fn:2]
*** Points you might run into
*** Points you might run into (Weaknesses)
- Steep learning curve[fn:4] compiler enforcing (esp. memory)
rules that would be "best practices" elsewhere.
- Missing Rust-native libs in some domains, target platforms