Apple Is Looking for Linux Kernel Developers
phoronix.com
phoronix.com
If you have, say, a farm of little ARM-driven devices that you use as test harnesses for chips or other hardware, it isn't necessarily cheaper to port whatever variation of xnu to this particular hardware than to use an existing port of Linux and hire some folks who can help with the low level I/O bits. There might even be Linux in your world because, e.g. an acquired company built something on it that hasn't been worth porting.
Or any of a ton of other possibilities.
Having an OS doesn't mean you have to use (variations of) it for everything, especially if the new use you're thinking about is far from your usual.
I've seen multiple people stop all their open source contributions and communicating online after being hired by them. I assume they have very draconian NDAs.
No major technology company open sources their Crown Jewels.
Source: ex-applers
These days, Apple's datacenters are running all sorts of things, including Darwin, Linux, Solaris, and AIX[1]. But the "Darwin" part is still essentially NetBSD, not FreeBSD.
[1] http://www.zdnet.com/article/tale-of-two-data-center-strateg...
I don't think most people say that macOS is built on top of a FreeBSD userland. Most people rightly point out that there is a lot of FreeBSD code inside the macOS code base specifically the XNU kernel[1].
> But the "Darwin" part is still essentially NetBSD, not FreeBSD.
That's incorrect while there is NetBSD code in MacOS. Dismissing the FreeBSD code, the Mach code, the code Apple wrote and saying that Darwin is essentially NetBSD is extremely disingenuous[2].
[1]: https://github.com/apple/darwin-xnu/search?utf8=%E2%9C%93&q=...
[2]: https://developer.apple.com/library/content/documentation/Da...
They're probably pushing into more vertical control there. Good guess.
They probably use Linux as extra validation for their chips.
https://daniel.haxx.se/blog/2016/10/11/poll-on-mac-10-12-is-...
On the other hand, it may work against us, having Apple involved in Linux things. I'm not sold either way - but I sit here, re-installing MacOS on two Macbook Pro's, both of which absolutely refuse to make a usable/safe disk image out of their own disks. This is such a frustrating conundrum, it feels like Solaris in the 90's. I can only hope something changes at Apple, or else I'm just going to wipe MacOS and put Linux on these machines. That is quite a watershed, imho.
I'm now trying to do a full update to the latest release, and see if it works beyond that point - but if it doesn't, the good ol' tarball approach is all I've got left.
I think Apple has some QA issues.
EDIT: https://twitter.com/stroughtonsmith/status/89096147427705651...
it's about chip validation and has nothing to do with MacOS etc, because it will be pretty unwise to use MacOS to check silicons.
This sort of ad seems to indicate they'd hire somebody to actually work on Linux stuff.
Kind of like WSL but instead main OS is completely locked down and instead of software emulation you get isolated hardware to run Linux.
Oh and by the way "perfectly good" is way too generous for the hypervisor macOS ships with, unless there have been recent drastic improvements..