4 ms·
> Only the author "knew" Rust and it was hard to justify a new hire Rust developer to maintain this small set of tools. There are two dialects of Rust. One can
by selfmodruntime 2y ago
> Only the author "knew" Rust and it was hard to justify a new hire Rust developer to maintain this small set of tools.
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.
- throwawaymaths 2y agoStrong "only use this subset of c++" energy
- iknowstuff 2y agoexcept using a different set of rust is not gonna allow RCEs or leak your data to the internet
- throwawaymaths 2y agoEh. An enterprising young developer could build an ECS style system with references as u32 indices and all bets are off.
- 01HNNWZ0MV43FF 2y ago"the worst of all are the stupid and diligent"
- sshine 2y ago> 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.
- selfmodruntime 2y agoNow with the Error trait in core, I'm hoping for `no-std` versions of `thiserror` and `anyhow`.