As everything, I think a bit of balance is needed.<p>You&#x27;re doing a quick MVP to demonstrate that your idea is working? Fuck it, just throw in dependencies for everything, just care about solving the problem you&#x27;re trying to solve and proving&#x2F;disproving your point.<p>Once you verified it, then go and kill your dependencies. But don&#x27;t do it just because you want to do it. If in the end the users doesn&#x27;t benefit from you optimizing your dependencies, why do it? (Speaking from a product side rather than a OSS project used by other projects)<p>Not sure KILL ALL DEPENDENCIES is helpful, but I&#x27;m not sure that MAKE EVERYTHING A DEPENDENCY is helpful either so...