5 ms·
Flies like an emulator, quacks like an emulator, waddles like an emulator: duck-typing says it's a bloody emulator.
by MaysonL 13y ago
Flies like an emulator, quacks like an emulator, waddles like an emulator: duck-typing says it's a bloody emulator.
- jvm 13y agoI'm not sure it virtualizes an x86 box running Windows like an emulator though.
- TsiCClawOfLight 13y agocome on... WINE is a compatibility layer. Nothing gets emulated in any way. You can check the FAQ, a sibling posted the link.
- mhurron 13y ago> Nothing gets emulated in any way Except for the Windows API, including all of its bugs and oddities. Emulation != Vitualization
- aclevernickname 13y ago> Except for the Windows API, including all of its bugs and oddities. Back in the day, us of the emulation community would refer to such things as "wrappers" (see, glide[1]). WINE definitely qualifies as a wrapper, as it merely translates one API to another. Darling seems to fit this same definition. Both are handling big API's, but that doesn't make it emulation when you reimplement them. Wikipedia's definition mentions hardware specifically as a requirement of Emulation [2]. In fact, they go even further to say that any software that duplicates the hardware of another machine should be considered a simulator [3]. This means that WINE and Darling are now twice removed from the Emulation family. [1] http://www.glideunderground.com/modules.php?op=modload&name=HTMLArticles&file=index&req=showcontent&id=89 http://www.glideunderground.com/modules.php?op=modload&name=... [2] https://en.wikipedia.org/wiki/Emulator https://en.wikipedia.org/wiki/Emulator [3] https://en.wikipedia.org/wiki/Emulator#Emulation_versus_simulation https://en.wikipedia.org/wiki/Emulator#Emulation_versus_simu...
- pmelendez 13y agoIt is not an emulator though... It is a reimplementation layer of winapi.
- epistasis 13y agoWine emulates an API, not a CPU or a machine. The original meaning of WINE was WINdows Emulator. [1] The word "emulator" in tech sometimes acquired an association with CPU or computer emulators. So for whatever reason (joke, marketing, etc.) WINE changed the meaning of the acronym. But it's still an emulator, just an API emulator rather than CPU emulator. [1] http://www.faqs.org/faqs/windows-emulation/wine-faq/ http://www.faqs.org/faqs/windows-emulation/wine-faq/
- networked 13y ago>So for whatever reason (joke, marketing, etc.) WINE changed the meaning of the acronym. It's likely they did it for the same reason for which "Windows Commander" famously had to change its name to "Total Commander": to avoid infringing upon Microsoft's trademark. Christian Ghisler got a letter from Microsoft's lawyers about the name of his file manager, though [1]; AFAIK, Wine didn't. [1] http://www.ghisler.com/name.htm http://www.ghisler.com/name.htm
- pmelendez 13y agoThat's a reference for the name but nothing is actually emulated on this. I find the wikipedia article explanation very appropriate: "The phrase "Wine Is Not an Emulator" is a reference to the fact that no processor code execution emulation occurs when running a Windows app under Wine. "Emulation" usually refers to the execution of compiled code intended for one processor (say, x86) by interpreting/recompiling software running on a different processor (say, PowerPC). " : ... In Wine, the Windows app's compiled x86 code runs at full native speed on the computer's x86 processor, just as it does when running under Windows. And Windows API calls and services also are not emulated, but rather substituted with Linux equivalents that are compiled for x86 and run at full, native speed."[1] [1] http://en.wikipedia.org/wiki/Wine_%28software%29 http://en.wikipedia.org/wiki/Wine_%28software%29