Linked by David Adams on Fri 18th Jun 2010 19:17 UTC
Linux Linux Magazine has a profile of Daniel Fore and the Elementary project. Elementary is a Linux distro that's committed to a clean and simple user experience, but it's more than a distro - it's actually a multi-pronged effort to make improvements to the user experience for a whole ecosystem of components, including icons, a GTK theme, Midori improvements, Nautilus, and even Firefox. The work that elementary is doing isn't limited to their own distro, and some of their work is available in current, and perhaps future, Ubuntu releases. The results are really striking, and I think it's probably the handsomest Linux UI I've ever seen.
Thread beginning with comment 430660
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: OMG that looks GOOD!
by WereCatf on Sat 19th Jun 2010 12:56 UTC in reply to "RE[4]: OMG that looks GOOD!"
WereCatf
Member since:
2006-02-15

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 ;)

Reply Parent Score: 3

RE[6]: OMG that looks GOOD!
by cerbie on Sat 19th Jun 2010 13:32 in reply to "RE[5]: OMG that looks GOOD!"
cerbie Member since:
2006-01-02

How about API layer?

Reply Parent Score: 3

RE[6]: OMG that looks GOOD!
by ndrw on Sat 19th Jun 2010 14:43 in reply to "RE[5]: OMG that looks GOOD!"
ndrw Member since:
2009-06-30

I don't mean anything negative with butting in the conversation

Sorry about that. You're more than welcome to join the discussion.


So, number 1 doesn't apply to WINE.

I think you're narrowing the definition a bit too much. Look:

emulate
2 entries found.

1. emulate (transitive verb)
2. emulate (adjective)

Main Entry: 1em·u·late
Pronunciation: \ˈem-yə-ˌlāt, -yü-\
Function: transitive verb
Inflected Form(s): em·u·lat·ed; em·u·lat·ing
Etymology: Latin aemulatus, past participle of aemulari, from aemulus rivaling
Date: 1582

1 a : to strive to equal or excel b : imitate; especially : to imitate by means of an emulator
2 : to equal or approach equality with


And since WINE does not indeed allow you to run x86 applications under non-x86 compatible hardware number 2 doesn't apply either.

Definition says nothing about the CPU type or the implementation.

Yes, internally WINE is just an independent implementation of Windows API. But, aren't VMWare or Bochs just software implementations of the x86 hardware interface? Isn't VMWare limited to x86?


Like f.ex. Mono isn't emulating .NET neither does WINE emulate WIN32, they're just new implementations of the same old thing.

Very interesting point. I would say that Mono isn't emulating .NET the specification but it is emulating .NET the implementation. In the end it's pretty fluid, depending which of these really defines the platform.

Finally, let's not be so fussy about a name. I've seen names like "Windows" or "Apache" applied to software products. ;-)

Reply Parent Score: 2

RE[7]: OMG that looks GOOD!
by chris_l on Sat 19th Jun 2010 17:20 in reply to "RE[6]: OMG that looks GOOD!"
chris_l Member since:
2010-02-14

Finally, let's not be so fussy about a name. I've seen names like "Windows" or "Apache" applied to software products. ;-)

Yes, let's *DO* be so fussy about a name when idiots like yourself try applying the *WRONG* definitions to the item in question.

Reply Parent Score: -1

RE[7]: OMG that looks GOOD!
by JAlexoid on Sat 19th Jun 2010 21:42 in reply to "RE[6]: OMG that looks GOOD!"
JAlexoid Member since:
2009-05-19


Like f.ex. Mono isn't emulating .NET neither does WINE emulate WIN32, they're just new implementations of the same old thing.

Very interesting point. I would say that Mono isn't emulating .NET the specification but it is emulating .NET the implementation. In the end it's pretty fluid, depending which of these really defines the platform.


WINE is an API/ABI abstraction layer. Why can't it be called an emulator? Because Windows is an OS and WINE is nowhere near that. Though WINE with Linux, as a tandem, could be called a Windows Emulator.

Yet, Mono does try to emulate MS.NET in all and every aspect, top to bottom.

Reply Parent Score: 2