2 ms·
Initially in the 1980s it was to distinguish it visually from the other entries in the directory to make it more likely it is the first file a newbie will read.
by hollerith 3y ago
Initially in the 1980s it was to distinguish it visually from the other entries in the directory to make it more likely it is the first file a newbie will read.
- 01HNNWZ0MV43FF 3y agoUppercase also comes first in ASCII, so a naive sort will show README before rEADME
- mannyv 3y agoOn *nix systems README was always the first file in the directory because everyone tended to use lower case for all their other filenames. 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).
- bqmjjx0kac 3y agoIn an alternate timeline, we could have named them MAKEME instead of Makefile.
- anthk 3y agoplan9/9front uses mkfile.
- timbit42 3y agoThis doesn't make any sense. All filenames were uppercase in DOS so having README in uppercase wouldn't distinguish it visually.
- hollerith 3y agoI claim the README convention came from Unix.
- kps 3y agoThis particular question is not about the origin of README files (the earliest documented is from 1974 on TOPS-10) but about why README remains upper case on mixed-case systems (e.g. Unix). Neither has anything to do with MS-DOS. ASCIIbetical order is a good answer (certainly the reason I named things that way) although it doesn't entirely explain README over ReadMe.