[jrgifford]

"OS X is very good at not having hardware compatibility issues" is a really, really old (and flawed) argument.

The thing that makes OS X so darn "stable" is that they write drivers for a very limited set of hardware - the reference implementation.

On the Linux reference implementation, everything works properly (See the ThinkPad T series).

On the Windows reference implementation, everything works properly (See the Surface).

Simply because something works when it's built for a piece of hardware (think embedded systems) doesn't mean that it will work when running on something that it wasn't designed for.

[superuser2]

>Simply because something works when it's built for a piece of hardware (think embedded systems) doesn't mean that it will work when running on something that it wasn't designed for.

No one is advocating doing that. And no one gives a shit about how hard it was for the engineers.

You should buy a Macbook precisely because it is a reference implementation that works as a consumer product. Let OSX deal with laptop-y details like WiFi, screen brightness, battery/power management, suspend/resume, and device drivers. Let VirtualBox abstract away those details so FreeBSD behaves like it does on its reference implementation - server hardware.

[RexRollman]

I've been doing that with NetBSD and VMWare Fusion on my 2013 Macbook Air with 8GB RAM. It's nice but I do miss running NetBSD on bare hardware.

OS X does add a lot of overhead and I would love to run NetBSD on a dedicated hypervisor. In particular I want to try with the free Hyper-V Server because it has such great hardware/driver support but HVS doesn't support wireless networking.