Hey @devcurmudgeon
The third of these could be a good way for you to do that "learn some haskell" you've been threatening to do :-D It's a gentle introduction while also being very handy.
I want to reply "Challenge accepted" since I know I'm good at eating Quavers. Sadly I also know I'm no good at crocheting, regardless of what I'm doing about food :/
I like to use words such as 'actual' or 'absolute' as emphasis, or 'suppurating' for the mouth-feel.
"What the absolute suppurating trashpile of a fuck is going on here?" for example
There may be a way to accelerate movement towards consensus, but if there is, I don't know it. I expect that at some point a large project overseeing many pieces of software will select some terms which will then, by osmosis, become de-facto. Just like Git did.
I see your point. I fear that we're likely to be in a bit of a churn on terminology until the zeitgeist settles again. Until then we'll have to apply a small amount more mental effort (annoying, but not the end of the world) :-)
In general it's possible to come up with a pair of terms which more correctly describe the relationship between systems, without using potentially contentious labels.