To view parent comment, click here.
To read all comments associated with this story, please click here.
emulator
Main Entry: em·u·la·tor
Pronunciation: \ˈem-yə-ˌlā-tər\
Function: noun
Date: 1589
1 : one that emulates
2 : hardware or software that permits programs written for one computer to be run on another computer
I don't mean anything negative with butting in the conversation, but I just feel like I could perhaps help clarify this. Yes, I do understand why people often liken WINE to an emulator; after all it does indeed let you run applications designed for a different OS under an OS they weren't meant for.
However, WINE does not emulate a computer. It does not modify application's code in any way, nor does it modify parts of the underlying OS either. Instead it just passes certain function calls to the underlying OS, and maybe adjusts the parameters sent in order for the function to work properly. The code of the application itself however is untouched. And WINE itself mostly consists of a reimplementation of WIN32 environment. Like f.ex. Mono isn't emulating .NET neither does WINE emulate WIN32, they're just new implementations of the same old thing.
So, number 1 doesn't apply to WINE. And since WINE does not indeed allow you to run x86 applications under non-x86 compatible hardware number 2 doesn't apply either.
What does that leave us with? WINE, a program that allows you to run software designed for Windows under Linux, what would a proper term for it be? I personally would call it Windows-compatible environment, or a Windows compatibility layer. Feel free however to offer any insightful comments or better phrasings if you feel inclined 
That is not the accepted definition that is currently in use in the industry.
The user contributed article from wikipedia, best describes the current definition in use in the industry.
http://en.wikipedia.org/wiki/Emulator





Member since:
2010-02-14
I guess GNU and WINE acronyms (or just N's in them) were adopted to avoid trademarks and to stress that no copyright violation took place (both products are independent reimplementation of some API's).
If not that, we'd probably settle for names like "Free UNIX" or "Windows Emulator".
Moron, have you *EVER* used WINE? It *DOES NOT* emulate
Windows. It translates Windows software calls into their Linux versions.
That's why Windows programs don't either work under WINE or don't work correctly. For instance if a Windows program makes use of the Windows firewall, odds are it won't work or not work correctly unless you can tell not to use it because the Linux firewall is not the same as the Windows one on a basic level.