Jordan Hubbard (of FreeBSD Fame) Hired by Apple

Anonymous Coward and many others wrote in to tell us that Jordan Hubbard is going to work for Apple. Here's his post to the FreeBSD-announce mail list.

Comments

List of thoughts on hubbard@apple.com

[maggard]

First off kudos to Apple for hiring a great coder. While they've already got some strong talent in-house more can't hurt. Besides which Hubbard's FreeBSD skills should come in great use keeping MacOS X compatible with the BSD's.

For those already posting wild-assed assumptions (like it would kill these folks to look up their own answers - this is the web!) here's a couple of responses bundled up:

• FreeBSD is *not* the basis of MacOS X. The kernel is different and the utilities are a hodgepodge from a number of BSD distribs.
• Darwin is the MacOS X core and it's freely available. Indeed Apple has ported it to x86 (a platform they don't sell) and provides it the same support they do their PPC implementation. It's Open Source, go grab a copy for yourself.
• Darwin is the core of MacOS X - it's NOT all of it. The Classic, Carbon, Quartz, QuickTime, etc. parts remain in house & aren't likely to be released. Some folks whinge on about Apple taking advantage of Open Source - well yeah, that's why folks used the licenses they did. On the other hand Apple's also been contributing back a lot too (unlike MS) and while they may not have released your favorite bits they've been playing fairly.
• Yes Apple has rabid lawyers when it gets to things that involve their name & IP, especially their "look". Sure imitation is the sincerest form of flattery, on the other hand they spenty a lot developing their look & it's their trade dress.
• There is no "secret agreement" between Apple & MS regarding using x86 (at least that anyone seriously believes.) MS makes good money off of their MacOS products and wouldn't likely be strongly impacted by Apple using x86. On the other hand Apple is very unlikely to do so for a long list of reasons. Finally any such agreement would get MS in to too much hot water.
• Porting BSD tools to MacOS X varies in difficulty. For simple command-line stuff it's pretty straightforward, indeed lots of stuff makes just fine already. On the other hand taking advantage of MacOS X's Cocoa OO environment with it's "services", "frameworks", "packages" and other nifty stuff takes a bit more work.
• For ports that do GUI there's some work involved in going from X to Quartz but it's entirely doable. X-under-Aqua is available but it's kinda missing the point of running MacOS in the first place. Java-stuff of course runs natively, uses the Aqua GUI via Swing.

What's Hubbard likely to do? There's a spot open for managing the Darwin porting. There's lots of BSD-harmonizing to do. Many parts of MacOS X are still being tuned so any help there is likely to be appreciated. There's also been a push to make MacOS X Server shine so that's also a likely source of work. Finally there's just basic evangelizing and developer relations.