4 ms·
Rustc is so big and slow because it does a lot. The problem with rust is that it's trying to compete with both c and node, and it has started to tilt more towar
by fctorial 6y ago
Rustc is so big and slow because it does a lot. The problem with rust is that it's trying to compete with both c and node, and it has started to tilt more towards node in recent years.
- BearOso 6y agoI like rust, but I detest cargo. I don’t like that it forces a particular structure that makes every project feel like a visual studio template. I also don’t like that it has an single authoritative registry that it pulls packages from on build. This means that someone somewhere has too much control over the build process, and that I can’t work where there’s no internet access.
- steveklabnik 6y agoJust so you know: 1. You can configure cargo to change the directory layout if you'd like 2. You can use alternative registries 3. There is an offline mode that will specifically not even attempt internet access.
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- edflsafoiewq 6y ago> Rustc is so big and slow because it does a lot. From the outside, it's hard to tell if this is true, or if Rust and rustc just consistently makes choices without valuing smallness or speed. The crate ecosystem definitely skews away from these and towards "grand abstraction".