Doesn't rust suffer from the same, way too wide dependency web?
I feel like its an unfortunate consequence of having a good package manager which encourages proliferation of too many very small dependencies.
I feel like its an unfortunate consequence of having a good package manager which encourages proliferation of too many very small dependencies.
I was playing with some Rust-based blockchain system, and the number of external dependencies pulled in (recursively) to build the code truly amazed me.
I don't really know, but I'm guessing that a similar C++ project would have required many fewer dependencies.
Maybe a C++ code base would tend rely on a small number of big libraries?
Or maybe a C++ code base would (for some reason) be more inclined to use binary libraries provided by already-installed Debian packages?
Sometimes I see single-header libraries you can just drop in, other times I see large Cmake projects that you add as a dependency to compile when your project compiles.
I've never seen the kind of dependency chaining that languages like JS or Go show.