Do you know what's not accessible? Writing "a11y" in any article or documentation
I will accept it as a convenience in APIs since developers are lazy and can't spell, but fuck off with using it in text
Do you know what's not accessible? Writing "a11y" in any article or documentation
I will accept it as a convenience in APIs since developers are lazy and can't spell, but fuck off with using it in text
@jtruk @jonathanhogg the general form (a11y, i18n, k8s) has been around a while now.
I think i18n came first, probably because it was easier than repeatedly having the "internationalisation vs internationalization" spelling debate...
But I have seen it said that "k8s" was first because no one could remember how to spell (or pronounce) kubernetes?
Either way, I absolutely hate that this has just become how the tech industry abbreviates things.
It feels like it's on the "smug" side of clever
@jonathanhogg @lpbkdotnet @jtruk But it helps sometimes: try to go a interoperability meeting and you'll see why saying "i14y" is much more pratical.
Whatever the case, in my texts I always put an abbreviation with the expanded term right in the beginning. If it's seldom used, I only write the expanded form.
@jonathanhogg @andrewt But that's normal. Every group will develop their own language and conduct, opaque to outsiders.
Just like a group of friends will develop their own stories and contexts.
It's only a bad thing when the discussion is meant to welcome outsiders.