Having a dozen packages where one will do, and having them do the same thing recursively means you need to spend 144 times longer dealing with such things.
Having a dozen packages where one will do, and having them do the same thing recursively means you need to spend 144 times longer dealing with such things.
This "144 times longer" number seems pulled completely out of thin air.
One company missed installing malware behind all the firewalls of most of the fortune 500 by less than a week.
We made a procedural change to the build process of a product that had been shipping for years.
The change hit our CI/CD 5 days before one of the big language package managers started spewing malware at us.
Package maintainer count bloat is a serious real world problem.
Ignoring it is negligent.
It may be the case that this preference for well modularized code leads to lots of disparate small packages in the ecosystem, but within the scope of a single project, I see no reason why modularization poses any intrinsic risk.