I would certainly go with ignorant. I stay away from Windows and, in
consequence, from .NET. I've heard about NuGet, but I haven't used it, so
I don't know if it is any good.
On the other hand, I've seen both strategies (large and small packages) in
use, and the better dependency resolution mechanisms and package building
tools, the better small packages work. I don't need to install plethora of
GNOME and Python packages, I just run `apt-get install exaile' and have it
installed. From programmer's perspective this works equally well; I may want
to include some specific part of Boost library, but I can also run `apt-get
install liboost-all-dev' and be done, and leave detecting the actual
dependencies to package builder's tooling.
On the other hand, I've seen both strategies (large and small packages) in use, and the better dependency resolution mechanisms and package building tools, the better small packages work. I don't need to install plethora of GNOME and Python packages, I just run `apt-get install exaile' and have it installed. From programmer's perspective this works equally well; I may want to include some specific part of Boost library, but I can also run `apt-get install liboost-all-dev' and be done, and leave detecting the actual dependencies to package builder's tooling.