3 ms·
RISR – Rust 1.0 was that language. It was already a significant reduction over some other languages: having no GC makes the language simpler implementation-wise
by GolDDranks 5y ago
RISR – Rust 1.0 was that language. It was already a significant reduction over some other languages: having no GC makes the language simpler implementation-wise than 95% of modern languages. Memory safety is then brought back in by ownership and lifetimes, but those _restrict_ what you can do, not the other way. In a way, Rust 1.0 felt like a minimal design that achieved the goals: great performance and low-level control with memory safety without GC.
(Okay, there were some stuff around traits and type inference that were not _strictly_ necessary, I guess.)
However, it was _not_ nice to use. Even with current Rust, which is a whole lot more ergonomic, there are many places that feel unnecessarily restrictive. Patterns that feel like they should work, yet they don't.
Do you have any better idea how to make this stuff better without extending the language? Or maybe "worse is better", in which case Rust is not for you?
Maybe you are looking after Zig? https://ziglang.org/ https://ziglang.org/
- scoutt 5y ago> "worse is better" Of course not! If I have to choose, regarding system/embedded programming languages, then I'd go with "less is better". > Maybe you are looking after Zig? Definitely Zig is under my radar too. Fortunately, after all, I'm not alone. Many others I hear from the industry feel the same way.