Or a lot of libraries, it feels really messy when a project has a bunch of dependencies.
Dependencies themselves are usually a problem which sometimes arise from behind the useful work of package managers, but also make the program deviate from standards more and more and it makes it less simple as well, as >>20597
points out, it's a soykaffest of features most of the times.
Other times it's that the libraries themselves are some sort of behemoth, for example webkitgtk.
Vim+lua+python+ruby is another example of library blowup, thankfully they are optional.
It's not that I'm against libraries. If a project uses curses, or SDL, or even gtk (a GUI library, I don't like GUIs), I don't care, they are standard enough. But sometimes I get a bunch of dependencies for really obscure libraries which I never know what they do, and those libraries are only required by this one program, and it means only work (I have to get out of my way) to find out what they do and if they don't have some nasty vulnerability that the developers (it being a rather obscure library) haven't fixed.
Nope, I don't feel at all comfortable around library abuse.