3 ms·
Rust is on this path as well, the small standard library pretty much forces people into using a ton of tiny dependencies. Compiling a rust project is exactly li
by baby 7y ago
Rust is on this path as well, the small standard library pretty much forces people into using a ton of tiny dependencies. Compiling a rust project is exactly like using npm and seeing a never ending list of deps
- gardaani 7y agoIt is also difficult to know which dependencies have unsafe code. There's good discussion about it on reddit: https://www.reddit.com/r/rust/comments/ekpa3i/is_anyone_concerned_about_this_deep_deep_nesting/ https://www.reddit.com/r/rust/comments/ekpa3i/is_anyone_conc...
- matheusmoreira 7y agoThe underlying problem is the lack of curation. Micro-dependencies that are widely used and have been reviewed for quality should be promoted to a group of standard packages. They'd still be dependencies like any other but they'd be officially maintained and installed by default. Another problem with npm: every package gets its own copy of its dependencies. Not sure if Rust does that.
- steveklabnik 7y agoCargo de-duplicates packages as much as possible, and only includes multiple copies if there are multiple incompatible versions required.
- vmchale 7y ago> every package gets its own copy of its dependencies. Not sure if Rust does that. It does something halfway in between, which is still a security liability.
- vmchale 7y agoIMO the main problem with Rust is that it's tied to cargo, which tries to link in multiple versions of the same crate.