ADVANCED COMPOSITING & RETOUCHING - Chapter 9, Exercise 2
Why "Free Means Strictly Better" Overlooks the Real Tradeoff
====================================================================================

QUESTION:
A colleague says "GIMP's plugin ecosystem is strictly better than
Photoshop's, since everything is free." Using this chapter's own warning
box, explain what this claim overlooks.

SOLUTION / EXPLANATION:

This chapter's warning box is explicit that free and paid carry a real,
honest tradeoff - it is not simply a case of one option being strictly
better than the other in every respect.

The colleague's claim focuses only on cost, which is a genuine and real
advantage of GIMP's ecosystem - but it overlooks what a commercial
Photoshop plugin's price is often actually paying for: ongoing,
vendor-maintained compatibility as Photoshop itself continues to update,
plus a support channel to turn to if something breaks or behaves
unexpectedly. That's a real service, not a nominal one.

GIMP's free scripts carry no equivalent guarantee. If a script stops
working correctly after a GIMP update - which this chapter names as having
genuinely happened at scale during the GEGL transition, when many older
Script-Fu scripts broke - there's no vendor obligated to fix it. The only
possible fix comes from whichever community member originally wrote the
script, and only if they happen to still be maintaining it. For some
widely-used scripts that's true; for many others, it isn't, and the script
simply stays broken indefinitely.

So the accurate framing isn't "free is strictly better" or "paid is
strictly better" - it's that GIMP's ecosystem trades away guaranteed
vendor support in exchange for zero cost, while Photoshop's trades cost for
that guarantee. Whether that tradeoff favors GIMP or Photoshop in a given
situation depends on how critical the plugin is to a workflow and how much
that guarantee is actually worth to the person relying on it - it isn't a
one-sided win for either side.

--------------------------------------------------------------------------
WHY THIS WORKS AS AN ANSWER:
It identifies specifically what the colleague's cost-only framing leaves
out (vendor-maintained support and compatibility), grounds this in the
chapter's own concrete example (the GEGL transition breaking scripts with
no one obligated to fix them), and reframes the comparison as a genuine
tradeoff rather than accepting or flatly rejecting the "GIMP is strictly
better" claim.