Tsoding's main lesson is how simple systems can be and the desire and demand for complex build systems is silly.
No it isn't. "Simple" build systems like Make don't solve many of the problems that "complex" build systems like Bazel do.
At my current company I tried to convince my boss at the start of our project to use Bazel (it's very difficult to change build systems once your project is big), because I knew from experience it would solve many problems we would eventually run into.
He wouldn't let me and wanted to keep things "simple". Guess what happened? Now we have to run dozens of hours of CI just to fix a typo in a comment. CI regularly breaks because people forget dependencies. Etc.
"The Rules of Crust
Every function is unsafe. No references, only pointers. No cargo, build with rustc directly. No std, but libc is allowed. Only Edition 2021. All user structs and enums #[derive(Clone, Copy)]. Everything is pub by default."
The least recreational languages are probably like Java,C#
He doesn't actually use rust "idiomatically". He calls this "crust":
1. Every function is unsafe
2. No references, only pointers
3. No cargo, just rustc
4. No std, only libc
...
I don't know if he is sticking to these rules throughout but that was the idea in the beginning of this project.
