Re:A review after using Rust on embedded in production for o...
by sshine on Monday October 14, 2024 @04:52AM
(#41835573)
> There are two dialects of Rust. One can be written immediately by beginners, the other is for experts.
I believe it's more like a spectrum.
I'm 3 years into my Rust career.
I started with .clone() everywhere.
Then I moved on to write highly async code with tokio and std.
Now I'm somewhere entirely unfamiliar, writing highly portable no-std Rust for bare-metal and wasm.
It takes some time to know the difference between std and core.
It takes some effort to write modular, allocation-free code (static allocations only).
It takes some rediscovery of what crates will work for you.
It's a steep curve, and I don't imagine everyone likes it.
Re:A review after using Rust on embedded in production for o...
by j-krieger on Tuesday October 22, 2024 @12:14PM
(#41915810)
Now with the Error trait in core, I'm hoping for `no-std` versions of `thiserror` and `anyhow`.
Re:A review after using Rust on embedded in production for o...
by throwawaymaths on Monday October 14, 2024 @12:10PM
(#41838894)
Strong "only use this subset of c++" energy
Re:A review after using Rust on embedded in production for o...
by iknowstuff on Monday October 14, 2024 @02:57PM
(#41840666)
except using a different set of rust is not gonna allow RCEs or leak your data to the internet
Re:A review after using Rust on embedded in production for o...
by throwawaymaths on Monday October 14, 2024 @06:13PM
(#41842638)
Eh. An enterprising young developer could build an ECS style system with references as u32 indices and all bets are off.
Re:A review after using Rust on embedded in production for o...
by 01HNNWZ0MV43FF on Monday October 14, 2024 @09:40PM
(#41844095)
"the worst of all are the stupid and diligent"
There are two dialects of Rust. One can be written immediately by beginners, the other is for experts.
I make sure to write scripts in the first dialect. It uses `clone` all over the place, does not make use of any async runtime, and makes extensive use of "anyhow" for error creation and logging.
I advise all my peers to do the same, if they find a need for Rust in tiny scripts or applications.