> you end up with very large dependency trees similar to JS. And we know how that went. The problem in the JS ecosystem is not the number of dependencies, but

> you end up with very large dependency trees similar to JS. And we know how that went. The problem in the JS ecosystem is not the number of dependencies, but the number of entities you have to trust. There is no real difference between having one big crate in a repo managed by one entity or fifteen small crates in a repo managed by one entity.