News for hackers. Stuff that matters.
Re:Windows NT Kernel Contributor Explains Why Performance is... by shubb on Saturday May 11, 2013 @07:14AM (#5690311)
One problem that the WINE project (windows emulator for unix)has is that windows is full of undocumented APIs, some of which might be really quite useful, which are used by windows internal developers.

For WINE, if you are going to write an emulator that runs Microsoft code (like the .net framework, or notepad.exe), you need to find the correct behavior of these undocumented APIs by trial and error.

For a developer on Windows, it is perhaps frustrating that MS identifies and solves problems with it's platform, but doesn't publicly release these solutions to you.

I work for some random company that makes an SDK, although I mostly make products using it. Many of our best features are hidden - we don't ship the header files with the SDK, but the symbols are there in the binaries. Someone doesn't think they are useful enough to justify the testing expense for a full release. I guess MS have the same thing.

Re:Windows NT Kernel Contributor Explains Why Performance is... by randomfool on Saturday May 11, 2013 @02:44PM (#5691620)
No. You can complain about insufficiently documented APIs, or internal APIs that you wish you could use but are not documented, but please do not complain about undocumented APIs that are used by Microsoft applications outside of Windows.

Ever since the monopoly rulings against Microsoft, they have had extremely strict internal controls preventing non-OS code from using undocumented APIs. If a DLL or EXE does not ship on the Windows client install disk, it cannot reference APIs which are not documented in MSDN. Full stop.

You're referencing an API that inadvertently didn't get documented, but everyone knows about it, has blogged about it and lots of articles mentioning to use it? Too bad. Either stop using the API or delay release by 3 months for the next MSDN update.

Re:Windows NT Kernel Contributor Explains Why Performance is... by wfunction on Saturday May 11, 2013 @02:07PM (#5691454)
> undocumented APIs

"undocumented APIs" != "a magic combination of function arguments"

Any function that's not documented can be called an undocumented API, any program has them -- Linux, Windows, whatever.

But you were talking about the argument combinations being undefined, not the functions themselves. What are some examples of that?

Re:Windows NT Kernel Contributor Explains Why Performance is... by shubb on Monday May 20, 2013 @06:53AM (#5736910)
Re:Windows NT Kernel Contributor Explains Why Performance is... by wfunction on Monday May 20, 2013 @10:55PM (#5741642)
What about them?
Re:Windows NT Kernel Contributor Explains Why Performance is... by mikevm on Saturday May 11, 2013 @07:52AM (#5690357)
>One problem that the WINE project (windows emulator for unix)

Wine Is Not an Emulator.

Re:Windows NT Kernel Contributor Explains Why Performance is... by fnordfnordfnord on Saturday May 11, 2013 @09:43AM (#5690560)
What shall we call WINE then? A "pretender"? I'm serious btw. I've never seen a good concise explanation of the way WINE works in comparison to say, an emulator. I have a fairly good idea myself, but I wouldn't want to have to give more than a very brief talk over it.
Re:Windows NT Kernel Contributor Explains Why Performance is... by gizmo686 on Saturday May 11, 2013 @10:19AM (#5690634)
From the WINE website: "Wine (originally an acronym for "Wine Is Not an Emulator") is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems, such as Linux, Mac OSX, & BSD. Instead of simulating internal Windows logic like a virtual machine or emulator, Wine translates Windows API calls into POSIX calls on-the-fly, eliminating the performance and memory penalties of other methods and allowing you to cleanly integrate Windows applications into your desktop." [1]

[1]http://www.winehq.org/about/

Re:Windows NT Kernel Contributor Explains Why Performance is... by wfunction on Saturday May 11, 2013 @03:57PM (#5691896)
> What shall we call WINE then?

tl;dr: compatibility layer

Re:Windows NT Kernel Contributor Explains Why Performance is... by fnordfnordfnord on Saturday May 11, 2013 @12:17PM (#5691069)
I should have been more specific. How would you introduce WINE to freshmen, not CS students who might need to study WINE in detail, but well, here's a specific case, college freshmen who are expected to install WINE and then install and use software such as LTSpice, DipTrace, etc.? Or, more generally, how to explain it to neophytes who are expected to become moderately sophisticated computer users who might need to use WINE, but will probably never be software devs.
Re:Windows NT Kernel Contributor Explains Why Performance is... by HardlyYakka on Saturday May 11, 2013 @03:59PM (#5691899)
Something like:

WINE is a translator that allows Windows programs (those that have an .exe extension) to talk to other Operating Systems.

or perhaps:

Many people need wine if you want them to work. A windows program on Linux is no exception.

Re:Windows NT Kernel Contributor Explains Why Performance is... by justin66 on Saturday May 11, 2013 @05:05PM (#5692098)
> WINE is a translator that allows Windows programs (those that have an .exe extension) to talk to other Operating Systems.

I'm sure the aforementioned freshmen would like a no-bullshit explanation for why "emulator" hurts the WINE people's feelings but "translator" does not. It's always been a mystery to me.

Re:Windows NT Kernel Contributor Explains Why Performance is... by HardlyYakka on Saturday May 11, 2013 @06:12PM (#5692301)
> no-bullshit explanation

Hah! Not really possible, especially considering that the project used to be called windows emulator:

  http://www.faqs.org/faqs/windows-emulation/wine-faq/

I'd say they've changed the meaning so they can reinforce that it's not just another virtual machine ( and that it's faster than one).

Which is true, it doesn't emulate another hardware architecture's calls, just the kernel and OS magic needed.

In that regard, think of say a console game or arcade game emulator on a computer- that will have to emulate the whole architecture of said game system as well as the game.

Contrast that to a game program for the the x86 architecture, but not for windows- you could run it natively on windows providing you change everything the game asks for that's part of the Gamesystem380 system into something windows understands, and vice versa.

Re:Windows NT Kernel Contributor Explains Why Performance is... by plorkyeran on Saturday May 11, 2013 @10:20AM (#5690638)
A reverse-engineered implementation of the Win32 API?
Re:Windows NT Kernel Contributor Explains Why Performance is... by fnordfnordfnord on Saturday May 11, 2013 @12:20PM (#5691075)
Now we'll also have to explain what an API is, and then add some details about the Win32 API.
Re:Windows NT Kernel Contributor Explains Why Performance is... by illuminate on Saturday May 11, 2013 @12:02PM (#5691013)
Not pithy enough.
Re:Windows NT Kernel Contributor Explains Why Performance is... by asveikau on Saturday May 11, 2013 @01:06PM (#5691245)
It's a set of libraries, and a loader for EXEs and DLLs. That's the simplest, most literal way I can think of to explain it.
Re:Windows NT Kernel Contributor Explains Why Performance is... by shubb on Saturday May 11, 2013 @08:16AM (#5690396)
@Mike - Yes, that is true enough.