>>17613
The most I'll consneed is that it's both possible and desirable for apps to be written such that it will gracefully degrade and disable features of itself that need certain libraries if they aren't installed (e.g.: networking, extra file format importers/exporters, UI [graphical or otherwise], audio, crypto), even AFTER build time WITHOUT the need for a separate package.
But if the choice for a given feature being implemented is between, say, bespoke bullshit GUI in SDL or HTML/CSS, versus something that integrates fully native widgets to whatever DE I'm using like Qt or wx, then the latter approach is 100% preferable. The only other acceptable option for UIs in particular is ports to each individual toolkit instead of hiding behind a single crossplatform toolkit, which is usually fine for Mac/Windows/mobile, but on freetard OSs it tends to result in that unpleasant "GTK app that looks and works slightly wrong at best on everything else" problem.
As long as it isn't using extra memory all the time, and isn't insisting on (or worse yet static linking!) its own speshul snowflake version (usually outdated CVE-laden) of a lib I already have, the extra storage space to have it installed nowadays is well worth having a standard implementation of a feature that works properly.