Comments on: PE U: The Mac OS X Leopard Windows API Myth

By: John Dvorak Conceeds 2007 was a “Crappy Year” for Windows Enthusiasts — RoughlyDrafted Magazine

Wed, 02 Jan 2008 08:38:45 +0000

[...] PE U: The Mac OS X Leopard Windows API Myth [...]

By: Advancing Software Reuse of Linux, Windows Code on the Mac — RoughlyDrafted Magazine

Mon, 17 Dec 2007 07:16:36 +0000

[...] PE U: The Mac OS X Leopard Windows API Myth Windows DLL Sharing? Responding to my comments in “PE U: The Mac OS X Leopard Windows API Myth” some developers wrote to suggest the idea that Apple may be building tools to appropriate portions of closed Windows code in the same way Mac OS X can make use of Unix/POSIX libraries. [...]

By: avocade

avocade — Fri, 07 Dec 2007 20:37:10 +0000

“The iPhone is making Apple millions of dollars in hardware revenues, millions more in service sharing revenues, and early next spring it will cast the Mother of All Halos over the development world, bringing more attention to Cocoa and Objective-C than ever before in history.”

Simply excellent.

By: links for 2007-12-06 | /dev/random

links for 2007-12-06 | /dev/random — Thu, 06 Dec 2007 23:21:13 +0000

[...] PE U: The Mac OS X Leopard Windows API Myth Article debunking the Windows API myth points out that executable format doesn’t imply a particular API. (tags: macosx Leopard) [...]

By: Mac Marc

Mac Marc — Thu, 06 Dec 2007 22:49:33 +0000

The analogy to time travel had me ROFLMAO! Thanks!

By: links for 2007-12-06 « Mike’s Blog

links for 2007-12-06 « Mike’s Blog — Thu, 06 Dec 2007 22:23:03 +0000

[...] PE U: The Mac OS X Leopard Windows API Myth Article debunking the Windows API myth points out that executable format doesn’t imply a particular API. (tags: macosx Leopard) [...]

By: Arrgh

Arrgh — Thu, 06 Dec 2007 18:33:42 +0000

I’m fairly certain it’s there to enable support for Mono, which on Linux uses PE executables and DLLs that are presumably only functional on Linux.

At least with Fedora each these PE binaries are normally launched with a shell script, but the Linux kernel has had support for loading foreign binaries for a very long time… If the magic number at the top of the file doesn’t look like ELF or a shebang, it will consult a list of mappings from magic numbers to launcher utilities. One very common use case is to register PE files as belonging to the WINE executable.

$ file /usr/lib64/tomboy/Tomboy.exe
/usr/lib64/tomboy/Tomboy.exe: MS-DOS executable PE for MS Windows (console) Intel 80386 32-bit Mono/.Net assembly

By: osViews | osOpinion

osViews | osOpinion — Thu, 06 Dec 2007 16:58:28 +0000

PE U: The Mac OS X Leopard Windows API Myth…

PE U: The Mac OS X Leopard Windows API Myth
Some ideas just won’t die. Proponents of the Mac OS X Leopard Windows API Myth are so convinced that Apple d…

By: API do Windows no Mac OS X Leopard é mito, afirma colunista | AppleMania.info

Thu, 06 Dec 2007 14:01:12 +0000

[...] explica todos os motivos em seu artigo completo. No momento da finalização deste artigo nosso iTunes tocava: Simple Minds, Alive & Kicking [...]

By: macpeter

macpeter — Thu, 06 Dec 2007 09:57:46 +0000

For Apple it will make more sense to develop a windows compilation box for xcode, so xcode became the favourite cross plattform development tool. Apple have more and more important windows application to support, e.g. itunes and safari. The easier it would be to develop vor Windows, the more Apple could port software to Windows, especiallly consumer products like iwork and ilife.. , but of course no stratigic and performance crictic pro software like final cut. That would have a whole bunch of benefits for Apple, it could earn money for software development from the microsoft market, and „microsoft onlys“ became familiar with Apple Software and last but not least Apple would become far more attractiv for 3rd party developers. And a wider range of software is the only favourite left for Windows at the moment.