Dependency minimalism (writing software that deliberately tries to have as few dependencies as practical) is a really underrated virtue imo.

Every single dependency is a risk that "something will go wrong" during someone's installation process. Installing projects with hundreds of dependencies and walking through errors can be incredibly frustrating.

This is idealistic thinking that helps steer progress, but realistically, productivity increases manyfold when people can build on each other's work. The same security argument can be applied to other parts of our lives, e.g. the food supply. I’d argue that this has the most severe implications when it comes to dependencies, yet society functions better when we can piggyback on each other. In the end, it all comes down to risk assessment.

Play 🎲 Win 🏆 Own 💰 -- Chancey is a fair, community driven, decentralized lottery.

https://www.getchancey.com/

Yeah, I think about this quite a lot... it's important to keep things simple... but as you're adding functionality it doesn't always make sense to keep reinventing the wheel.  Why rewrite something that already works really well?