There's a long-running problem where more smaller dependencies is actually better but it intuitively *feels* worse to a lot of people, and I wonder whether anyone is working on resolving that UX problem
@joepie91 but I have no clue how one would even approach resolving that through UX, especially since I'm not entirely convinced that more smaller dependencies is generally better
IMHO, as long as we design, structure, and distribute software in (roughly) the manner we do now, there will be tradeoffs to small/big dependencies
@pinoaffe While technically true, this isn't what people are actually complaining about, and these complaints are most frequent in the context of JS - which *does* have that tooling.
It's purely the "oh no the dependency count is so high" that sets people off, no further reasoning beyond some vague assumptions about how that means more risk (that they cannot substantiate).
@joepie91 I guess that one way to mitigate this intuition is to showcase and pay attention to the size of the "interface" of a library, I think people will intuitively see a big number as a bad thing and would thus rather depend on a specialized library/tool than a behemoth
@joepie91 imo there are some real negative aspects to having lots of small dependencies if you don't have good tooling, and (the ecosystems around) functional package managers/build systems such as guix and nix are working to combat that