is there a *compelling* use case for "FILESEXTRAPATHS_append"?
Robert P. J. Day
over the years, i've always been uncomfortable with the admittedly
small number of examples in various layers i've found that append to
FILESEXTRAPATHS rather than prepend, so i'm curious if there is an
actual, persuasive reason to ever do that.
philosophically, when one uses FILESEXTRAPATHS_prepend, one is
effectively saying, "here, use my content. nobody else's. mine. it's
right here. you can see it." and there should be no ambiguity, of
when you append, however, you're allowing for some hitherto unknown
earlier layer to jump in and override some of your content.
effectively, it seems (and i'm willing to be corrected) that you're
saying, "i have some content that *could* be used, but if some earlier
layer has the same content, we'll use that instead."
that seems to open up a huge can of non-determinism, if an earlier
layer suddenly introduces (or, conversely removes) content of the same
name without you noticing, and weird things start to happen.
so the question is, is there a really, well-defined use case for
appending to this variable?