I learnt this lesson dealing with Windows DLLs back in the VB days. More dependencies == less sanity. I've written Node/React web applications that break compl

I learnt this lesson dealing with Windows DLLs back in the VB days. More dependencies == less sanity. I've written Node/React web applications that break completely after a few months of not being updated, and after a year or more they need refactoring to remove deprecated/dead dependencies. And they always come with half a dozen security warnings that are impossible to get rid of. I've seen the default Go linter aggregator have to drop half the linters because no-one updated them to use generics. It's annoying, but not so much that I want to dive in and fix someone else's linter. I've spent hours learning the interface for ${useful library}, only to find they changed it in the latest release and they're not maintaining the old version. And I'm certain that the massive use of dependencies will cause a huge security problem this decade. Best account I've read of this: https://medium.com/hackernoon/im-harvesting-credit-card-numbers-and-passwords-from-your-site-here-s-how-9a8cb347c5b5 https://medium.com/hackernoon/im-harvesting-credit-card-numb... I use as few dependencies as possible these days.