Not all dependecies are "xz" complexity. Minimizing dependencies, probably means keeping a few libs things like crypto or compression and such. But do you nee

Not all dependecies are "xz" complexity. Minimizing dependencies, probably means keeping a few libs things like crypto or compression and such. But do you need a library to color console output? Even if colored console output is a business critical feature, you don't need a (tree of) dependencies for that. I see so many, rather trivial software that comes with hundreds or thousands of dependencies, it's mind boggling really. Why have 124million people downloaded a rubygem that loads and parses a .env file, something I do in a bash oneliner? Why do 21k public npm packages depend on a library that does "rm -f"? The answer, I'm afraid is mostly that people don't realize this isn't just some value added to their project but rather a liability. Some liabilities are certainly worth it. XZ is probably one of them. But a Library that does "rm -f" certainly isn't.