3 ms·
It is a fallacy that you are not maintaining something with your dependencies. It is the hope that you get nothing but benefits from depending on someone else
by taeric 10y ago
It is a fallacy that you are not maintaining something with your dependencies. It is the hope that you get nothing but benefits from depending on someone else to build strong dependencies. It is as true of a reality that they are pursuing goals that are not yours.
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.
- reikonomusha 10y agoYou are maintaining the API boundary between your application and your dependencies. I certainly do not maintain (in the most common sense of the word) my operating system source code, my compiler source code, my server source code, etc. 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.com/blog/?p=1936 http://web.archive.org/web/20140711172208/http://symbo1ics.c...
- TeMPOraL 10y ago> my operating system source code, my compiler source code, my server source code, etc. 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.
- taeric 10y agoExactly. And I wasn't trying to be anti micro services or libraries. Just pointing out that confirmation bias is a big reason some folks are against them. It is amplified when folks push them with no caveats. Some of us remember being burned in ways this allowed.