← Back to context Comment by staminade 2 months ago And all those 5 remaining dependencies have lots of dependencies of their own. What's your point? 8 comments staminade Reply koakuma-chan 2 months ago > What's your point?Just defending Rust.> 5 remaining dependencies have lots of dependencies of their own.Mostly well-known crates like rayon, crossbeam, tracing, etc. johnisgood 2 months ago You cannot defend Rust if this is reality.Any Rust project I have ever compiled pulled in over 1000 dependencies. Recently it was Zed with its >2000 dependencies. koakuma-chan 2 months ago I think it's justified for Zed. It does a lot of things. 5 replies →
koakuma-chan 2 months ago > What's your point?Just defending Rust.> 5 remaining dependencies have lots of dependencies of their own.Mostly well-known crates like rayon, crossbeam, tracing, etc. johnisgood 2 months ago You cannot defend Rust if this is reality.Any Rust project I have ever compiled pulled in over 1000 dependencies. Recently it was Zed with its >2000 dependencies. koakuma-chan 2 months ago I think it's justified for Zed. It does a lot of things. 5 replies →
johnisgood 2 months ago You cannot defend Rust if this is reality.Any Rust project I have ever compiled pulled in over 1000 dependencies. Recently it was Zed with its >2000 dependencies. koakuma-chan 2 months ago I think it's justified for Zed. It does a lot of things. 5 replies →
> What's your point?
Just defending Rust.
> 5 remaining dependencies have lots of dependencies of their own.
Mostly well-known crates like rayon, crossbeam, tracing, etc.
You cannot defend Rust if this is reality.
Any Rust project I have ever compiled pulled in over 1000 dependencies. Recently it was Zed with its >2000 dependencies.
I think it's justified for Zed. It does a lot of things.
5 replies →