Looking forward to the day that an actual, genuine discussion can be had about "minimizing dependencies" and what that entails, instead of the horde of "just make number low, problem solved" arguments that always happen in practice and completely ignore important things like internal complexity and peer review
Follow
"you"
Or to phrase it differently: we'll talk about "minimizing dependencies" when you show you understand how to minimize your *project complexity* first
"you"
@joepie91 Impossible to even answer the question of "too many" without knowing what they are and what they're doing. And there's definitely such thing as "too few". Including those parts you should have split into its own package because they're generically useful and someone else would need to reinvent the same thing.