It is odd, because the "micro library" world ostensibly fixes this by greatly limiting the scope of a dependency. However, it also encourages chaining yourself to many other entities. And it is always the mistakes that people remember, such that anyone that has been burned will remember how it was enabled by micro libraries.
I have no problem with micro-libraries. In fact, I developed on the notion of the micro-est of libraries: a library generator that gets down to function-level dependencies [0].
[0] http://web.archive.org/web/20140711172208/http://symbo1ics.c...
Actually, you sort of do. You may not know it yet, if you were fortunate enough to never hit a problem with an update to one of them.
It is amplified when folks push them with no caveats. Some of us remember being burned in ways this allowed.
While there are some folks [1] that have the time, energy, and brilliance to build things from the ground up all themselves, I unfortunately do not. Moreover, in a collegial work environment, this means the burden is on me to test, document, communicate, and educate on this library. There's enormous additional complexity and risk that comes with building from scratch things like these which change the whole programming paradigm of your application—again, especially in a coworking environment.
[0] https://en.m.wikipedia.org/wiki/Not_invented_here
[1] Donald Knuth and Fabrice Bellard, to name a few.