Doesn't linux stand for "linux is not unix"?
>Linus Torvalds had wanted to call his invention Freax, a portmanteau of "free", "freak", and "x" (as an allusion to Unix). During the start of his work on the system, he stored the files under the name "Freax" for about half of a year. Torvalds had already considered the name "Linux", but initially dismissed it as too egotistical.[13]
>In order to facilitate development, the files were uploaded to the FTP server (ftp.funet.fi) of FUNET in September 1991. Ari Lemmke at Helsinki University of Technology (HUT), who was one of the volunteer administrators for the FTP server at the time, did not think that "Freax" was a good name. So, he named the project "Linux" on the server without consulting Torvalds.[13] Later, however, Torvalds consented to "Linux".
>To demonstrate how the word "Linux" should be pronounced ([ˈliːnɵks]), Torvalds included an audio guide (audio speaker iconlisten (help·info)) with the kernel source code.[16]
I named my son, "Alistair", and there seems to be a million ways people pronounce that. He doesn't seem to care either.
The effort is appreciated but it's grating and she often ends up kindly telling them 'use Joanna instead'.
But that doesn't mean using the rules that language uses to translate the letters to phonemes! For example, English has a perfectly good sound for /i/ - so don't read foreign names with that sound in them as /ai/, just because the Latin spelling of said foreign name would be pronounced that way if it were an English word.
For example if you say "Australia" in an Australian accent, Japanese people probably wouldn't understand. So you'd have to use the "correct" Japanese pronunciation: "oh-su-to-ra-ri-a".
Another example is "Hyundai", which seems to have at least five different pronunciations. Apparently Koreans say "HYUN-day"[1], while the British say "high-UUN-digh", Americans say "HUN-day"[2] or something like "Han-die" in Spanish-speaking parts. Australians say "he-UN-day"[3]. Note to prescriptivists that this is how Hyundai's various subsidiaries say it in ads.
[1]: https://www.bbc.com/news/blogs-magazine-monitor-25813198
While my American cohorts refuse to use the same vowels, choosing “Lie” for the first syllable of the man’s name, and “Lih” for the first syllable of the kernel. Then berate me for following the pattern but using US English pronunciation rules.
But you guys know what I’m talking about, so just shut up and let’s get on with this deployment, mmk?
Also me, to myself: hold our beer we’re going to nerd snipe ourselves and write this as a regex that can’t be flagged as ReDoS.
/G(N)(U) is \1ot \2nix/I guess Worlds Most Efficient Security Violation Generator was tool long (WMESVG)
I just checked the PHP CVEs, amd it seems it has gone quite a while without high scoring CVEs - so, good for them
The original author first was going to call it winemu, but didn't like that. He shortened it to "wine", which led him to think of "whine" and "whinny". He liked "whine" but thought that was too long so "wine" it was.
The first suggestion of "Wine is Not an Emulator" was in 1993, when there were concerns Microsoft might raise trademark objects to "Windows Emulator". No one took that name suggestion seriously.
It wasn't until 1997 that it was adapted, as an alternative. In late 1997, the Wine FAQ said
> The word Wine stands for one of two things: WINdows Emulator, or Wine Is Not an Emulator. Both are right. Use whichever one you like best.
The shift to not mentioning it being a Windows emulator happened later. The release notes for 981108 said
> This is release 981108 of Wine, the MS Windows emulator.
and for 981211 said
> This is release 981211 of Wine, a free implementation of Windows on Unix.
As far as I've been able to glean from old Usenet posts, there were two reasons they stopped mentioning it being an emulator.
1. It could be used for more than just running Windows binaries under Unix. If you had source to a Windows program you could compile it on Unix and link it with Wine to give you a port of the Windows program. Wine was now a Windows compatibility system that included more than just an emulator. It was an emulator and a porting library.
2. Computers were getting fast enough that people were starting to run hardware emulators to do things like run game binaries from old consoles or old personal computers. Such emulators were not very fast. This might lead users to think that emulation was inherently slow, which might turn them off from trying Wine under the mistaken impression that it too would be slow.
Wine, when used to run Windows binaries rather than as a library when porting, is in fact still an emulator just like it was when Bob Amstadt first wrote it. Nothing technical changed when they added the backronym, or changed the text for the 981211 release notes.
But now we have plenty of people who have only ever seen the backronym, and the only emulators they have used that call themselves emulators have been emulating hardware, and so will insist that for something to be an emulator is must be emulating hardware.
Still, even today people tend to think of emulation as implying some sort of required slowdown. Unlike something like ARM or console emulation, most slowness in Wine has just been bugs rather than an inherent limitation of the concept.
Interestingly, I’ve never heard that anywhere else since.
Linux is far closer to “Linus’s Unix” (and that may actually be how it was named) than it would be to Linux is not Unix.
I once suggested an alternative: “Powering Hypertext & Programs” (https://alanhogan.com/conversations/php/acronym)