However, I wonder if a project similar to Wine will be needed in a few years, to run OSX applications.
However, I wonder if a project similar to Wine will be needed in a few years, to run OSX applications.
I used to have Windows and xwin32 and I would run my stuff on FreeBSD or Linux, and use Windows as my "mainstream OS when I needed to print things and/or listen to things."
Eventually my gear could run the Linux server in a virtual machine. Then I started running Windows in a virtual machine to avoid browser vulnerabilities (create a clean instance, browse for a while, then burn it).
I am almost to the point where I can boot Linux natively and run Windows in a VM (except for the occasional game) but I do less of that so its not as big a deal. I did an Atmel seminar where the whole time my "windows" machine was just a VirtualBox instance running full screen on my Lenovo T430. That was a perfectly acceptable experience.
I'm assuming it'll break, but what difference between the two OS's makes it break?
Not exactly. Mac OS does include a BSD subsystem and behaves more like a Unix than it behaves like Windows. But it is still significantly it's own thing.
The Mac kernel is XNU. Nearly all Mac apps use Cocoa. The Mac filesystem is HFS+. Hardware is managed through IOKit. The list goes on but basically every major system service is written for Mac OS and does not have any direct compatibility with other OSes.
More to the point, there's the lack of Mac-specific frameworks (e.g. Cocoa) on which most Mac applications rely.