If thought about properly, it doesn't. If you pull in a dependency on Xlib because you wanted a matrix math function from a graphics library, then it does. If

If thought about properly, it doesn't. If you pull in a dependency on Xlib because you wanted a matrix math function from a graphics library, then it does. If you're building on a platform that emphasizes many small libraries, and you pull in a few well-reputed ones, only to find that your dependency graph now includes 15 small buggy libraries hosted on github and abandoned by their developers, then it does. If you introduce a dependency on a Windows-only library in your game's physics engine, and then want to port the game to Linux, then it does. It's possible to be sloppy with using libraries, but I don't think academically-grounded programmers are any prone to being sloppy.