Mach/Darwin Binary Compatibility Hacker Interviewed
chromatic writes "Following up on an earlier story on NetBSD's fledgling Mach and Darwin binary compatibility layer, I've interviewed Emmanuel Dreyfus, who leads the project. The key questions are "what is it?", "what is it not?", and "what does it mean?""
So, now I can run Darwin/OS X apps on my mac. Cool.
I am a bit sketchy on Dreyfus's comment about NetBSD/Darwin compatibility requiring a Mac OS X user license.
From the article: "Therefore, in order to run a dynamically-linked application, you need the libraries from the emulated OS. The libraries are part of the emulated OS, and if you use them, you need a license for it."
It means you need a Mac OS X license ($0 with your PPC G3 or G4 processor based Macintosh computer unless it came with Mac OS 8.x or 9.x) to run Apple's implementation of the WindowServer libraries. You don't need such a license to run Cocoa binaries if and when somebody writes a WindowServer API compatible wrapper around gnustep.
Will I retire or break 10K?
Some people seem to think it is slow. Not just Mach- it's usually a generalization made across all message passing microkernels vs. monolithic kernels. And a lot of times, it probably is a wee bit slower, but the argument that what is gained makes it worth it.
Working toward a usable PDA environment in the spirit of Newton OS: Dynapad