3 ms·
Some people question when I've decided to only use a handful of dependencies in a project - usually "You could do it so much faster if you used X, so why not?"
by zdw 6y ago
Some people question when I've decided to only use a handful of dependencies in a project - usually "You could do it so much faster if you used X, so why not?"
The problem is that every dependency is a possible source of failure. For most languages, you can do a whole lot if the standard library is well-written - Python 3.6+ is particularly good for this, PHP if you don't mind API strageness, whereas Go without modules is less convenient, and outliers like node.js are basically unusable.
Also, frequently you don't need the popular "everyone uses it" libraries. For python, requests isn't needed anymore, as built-in urllib is quite good now and lacks a lot of "smart" functionality that causes strange breakage. pytest has more rough edges than built-in unittest. The only things that I use regularly that legitimately add functionality are pyyaml and tox (only when testing!).
- classified 6y agoFunny that you should call node.js an outlier when it's all the rage these days. Node does, however, go to show that short-term convenience trumps reliability and long-term stability by a wide margin.