Re: Jailbreaking?
{Continuing to dig myself in after the Bank Holiday...}
Thank you for so clearly illustrating WHY we end up with short (and conflicting) file name extensions:
> I'll use however many characters I need to be clear about what's in the file to myself and to those I'm sending the files to. To myself and the people I interact with, .md as markdown is easily understood
So if anyone is not sure what the extension is, they are part of the In Crowd and have trivial access to the explanation; I'd venture that there's a good chance the meta-data about what .md (or any other extension or piece of jargon) is used for is being passed on almost automatically and unconsciously "I'll send you a Markdown file, it is called fred.md".
> If I invent a new format, that one might get a longer extension to distinguish it.
Might. Note lack of "I make a deliberate and conscious descion about how this may be affected in the future" - like "next week when the company is bought out, everyone but me is sacked and I fall under a bus after drowning my sorrows". Or, less enjoyable, survive the bus and spend the next six months answering the same
> I'm not lengthening existing standard ones when the short versions work well enough
"well enough" - hmm, see below for "historical interest"
And there is a whole argument about what "standard" means - and the process by which they are reached (de facto, de jure etc). For .md a massive factor has been the single-sided, undiscussed decision for Github to automatically render files called readme.md (and those have affected what "Markdown" even means, as they use "Github flavored Markdown" - oh, look, at least once they've completely chucked out the parser they use and modified the accepted syntax in doing so (after all, why continue using an existing C library like a pleb when they can write from one scratch in Ruby? After all, if they enhanced the C library then hoi polloi can benefit). So .md should just be "Github flavor (whatever that might mean today) Markdown"!
When asked, John Gruber replied the only file extension I would endorse is “.markdown” - and then many a "discussion" has happened where people are so incensed that they even question whether Gruber should even be acknowledged on the matter.[1] Ah, people, people.
> the choice of extension doesn't matter much to the average user
The "average user" never types a file extension, they use GUIs that whack it on automagically; they probably don't even have the file extension visible in the file browser.
> Yes, I know there are plenty of historical cases where .md was used for something else ... or of mostly historical interest, so they don't constrain my choices now.
I.e. "*I* don't have any of those files in active use! I'm alright, Jack and sucks to be you, eh." Because, of course, the fact that the other uses may be considered "historical" *now* excuses the conflicts when the exension was first (re)coined: Markdown is over 20 years old, which makes it pretty "historical" itself!
I bet you can guess what I think of the Rust people, who think that even .rust is too many characters for their poor weak and feeble fingers to type!
[1] and if anyone knows what is supposed to be the issue between John Gruber and Guido (guessing Guido van Rossum), a deep and shameful part of me would be interested in the gossip
PS
In all of this, notice that I've accepted that .md is used - I don't *like* it (gee, yah don't say) but the main point is that people are *still* re-using these short extensions and there really is no reason for doing so - as noted above, there really are very few times nowadays when you actually have to type out an extension in full (as if typing is a hard thing to do...)