One thing I never see talked about online when it comes to dependencies is the cost of using dependencies. You often hear about the cost of "reinventing the wheel" and the apparent dangers thereof, but never anything about the cost of dependencies. I'll illustrate with an example, you want to parse XML so you import an XML parser library that has 10 other dependencies, those dependencies have dependencies etc, this is potentially a super-linear curve that grows with the number of dependencies (e.g. any fucking Rust library). That's the cost in terms of compile time but the worst comes for implementation code using a library. Any sufficiently advanced library meant to handle a real workload is bound to handle every reasonable edge case that users might encounter, so the complexity of a library for general purpose use will be at least a magnitude greater than hand-written code that serves a single purpose for a single user. So you wanted to parse some XML files, maybe you only needed a subset of XML, maybe not, but what you got was 100,000+ lines of code you now depend on for parsing XML and a complex API boundary written by some do-it-for-free GitHub janny. So what did you really gain from using the dependency? Nothing, in fact it's added negative value.