3 ms·
IMO, Rust isn't going to scale well * horrible syntax * crates.io is a graveyard of typo-squatting and lacks quality control, and no vendors / namespaces * s
by throwaway234623 4y ago
IMO, Rust isn't going to scale well
* horrible syntax
* crates.io is a graveyard of typo-squatting and lacks quality control, and no vendors / namespaces
* slow compilation
* standard library doesn't have HTTP, requires third-party libraries that are still immature / suck.
* widespread & prevalent abuse of .unwrap()
* error handling sucks because rust lacks set-theoretic types
* rust's async doesn't mesh with structured concurrency
* rust's async requires third-party libraries like tokio
highlights of rust
* pattern matching + ADTs
* move by default
* affine types
* concurrency & parallelism are easy
* serde crate
* kube crate
* rayon crate
- zanellato19 4y agoRust has already scaled well.
- ssokolow 4y ago> * standard library doesn't have HTTP, requires third-party libraries that are still immature / suck. > * widespread & prevalent abuse of .unwrap() [citation needed] > * rust's async requires third-party libraries like tokio As opposed to baking Tokio in and having people lament that they can't replace the executor for stuff like embedded use-cases? I remember hearing that there's interest in using async/await inside the Linux kernel with a custom executor.