Readme.txt vs. README.txt (2015)
softwareengineering.stackexchange.com
softwareengineering.stackexchange.com
During the sharing, hacking, free software period it was a lot less standard and I saw plenty of alternate casing for README and "non-standard" spellings like 00README, Readme_first, etc. When everyone started sharing their open source projects in a standard way (Github and its ilk, along with the rise of CTAN/CPAN-like registries for all kind software) the notion of the standard README got a lot more... standard.
The missing space is probably from UNIX preferences.
Note the assumption that any real user is able to read text files after classifying them as such no matter what their “extension” is. Also seen in countless "ORDER.FRM", "EXAMPLE.001", "EXAMPLE.002", and so on, not to mention all the ".DOC" files which had nothing to do with Microsoft Word.
8 for the "name" and 3 for the extension. ah, the lagacy of bit-counting when hardware was THE limitation on software
READ.ME just looks cool, same thing as with internet domains.
Edit: I even remember seeing this somewhere as a child and admiring how clever it was (Commander Keen maybe?).
And the capitalization thing in this case is of course also a DOS thing (as opposed to the newer traditions pointed out by another comment.
Tangent: on DOS and Windows, filenames without a file extension suffix were just weird. I mostly expected them to contain binary data :D
http://read.me/ I'm not interested, but it definitely looks cool
Say, you're connecting to BBS with A LOT of files. Unless you already know that "SEX459W.ZIP" and "SEX454.ZIP" are Windows and DOS versions of (fictitious) “Super Extractor 4.5”, you'll spend a lot of time figuring it out. People who pay no attention to file categories can also get intrigued without a cause. Therefore, full names and descriptions were stored in sidecar files, and were processed to form complete file listings (to download and study offline). Sometimes operators personally reviewed the software, adding interesting opinions about users who had it on their computers, sometimes those were simple excerpts from release notes.
In some cases, the metadata was automatically appended to archives (as standard comments). Later, in the era of Rich Formats, WinZip even allowed arbitrary HTML in ZIP comments, and automatically loaded them into IE frame instead of regular text box when opening such archive. Obviously, that novelty didn't last long.
Pretty sure the .DIZ stood for “Description In Zip”
http://catb.org/~esr/jargon/html/R/README-file.html
In fact, the revision history last shows an update in 2003.
The web site is old, but its merely the current incarnation of something much older: “The Jargon File (hereafter referred to as ‘jargon-1’ or ‘the File’) was begun by Raphael Finkel at Stanford in 1975.”
at the very least just copy the old readme and add a note on top. And please please keep it updated
I don't foresee that advice ever changing lol
Another example is FILE_ID.DIZ. Just learned the extension is for description in zipfile.
I believe "Makefile" tended to be capitalized too, since you generally wanted to look in there to see how to build the thing.
I don't think anyone wrote that down, it's just how things worked out. If anything it probably was inspired by Alice in Wonderland (Eat Me/Drink Me).
Next step is cleaning stuff up in a way that would make automatic documentation generation useful.
I tried to hack my way around fixing this a few years ago, but after many hours gave up.
But, full disclosure: I have never done it myself.
README.TXT vs README.MD:
https://stackoverflow.com/questions/8655937/what-is-the-diff...
The sorting trick is neat, though.
And that's what README.md files from these days hardly can follow on Github.
I assumed it was to sort at the top of 'ls' output, which is one of the answers on stack exchange.
https://developer.ibm.com/tutorials/l-linux-shells/
Early on it used esc instead of tab.
I also found in the bash changelog from 1996 there are fixes to crashing bugs in file name completion.
However, I stand by what I said. It was common for people not to know about filename completion. It was common to ship without it by default. Most clued in people installed bash on those systems. But not everybody.
Now I love them, but I've grown to love simple, "dumb" solutions.
Thanks.