Virtualization.framework isn't particularly limited, for what it is... given they're using Firecracker on Linux, it makes sense to use a similarly high level API on macOS.
(One could add a Hypervisor.framework backend to Firecracker, though I'd be surprised if AWS accepted it.)
Plus show me an off the shelf solution to MDM that exists in the Linux space?
(Not too mention an easy to buy consumer devices which supports suspend/resume correctly in 2026, not even Windows can do that any more)
Apple is crap and evil about many things, but at least here they know their paying audience...
One case where Apple can be very useful is if you're traveling a lot for work.
Wherever you are you can probably find a local store that sells and services Macbooks. So if your machine is damaged during a trip you can get it fixed, or buy a replacement on the spot, and at least get through the work you are there to do.
For small-ish companies that can be a very useful feature.
Four years on a shared remote machine before building the local backend is a good lesson in when to invest in dev tooling versus living with the workaround.
I just encountered the `com.apple.private.virtualization` entitlement limitation just last night, wanting to use VZVirtualMachine private AccessorEndpoint api. There's lot of useful stuff hidden in Apple's Private API space.
Great write up! I enjoy seeing others working in the same problem space.
(One could add a Hypervisor.framework backend to Firecracker, though I'd be surprised if AWS accepted it.)
They are solving the wrong problem.
Plus show me an off the shelf solution to MDM that exists in the Linux space? (Not too mention an easy to buy consumer devices which supports suspend/resume correctly in 2026, not even Windows can do that any more)
Apple is crap and evil about many things, but at least here they know their paying audience...
Wherever you are you can probably find a local store that sells and services Macbooks. So if your machine is damaged during a trip you can get it fixed, or buy a replacement on the spot, and at least get through the work you are there to do.
For small-ish companies that can be a very useful feature.
Great write up! I enjoy seeing others working in the same problem space.