Hacker News Reader

Comment by xnx | Hacker News Reader

Would love to see this mean the return of Bootcamp, but that's probably gone forever.

Boot camp is a windows problem. This can be done today on apple silicon but Microsoft dosent want to go through the effort to support it.

I imagine it would be a big lift. Asahi linux is managing through reverse engineering the hardware support, without any official documentation. Even with official documentation it would be a significant change from other aarch64 hardware.

I'm curious why I would want to dual boot Windows when there's a perfectly good hypervisor and paravirtualization built into macOS?

Arm-based windows support via Parallels does work, but AFAICT there's no official way to buy a Windows license due to a Microsoft/Qualcomm partnership.

No RAM, CPU, or disk overhead.

You can buy an ARM Windows license for parallels on Mac now. It works quite well.

I think WoA used to be exclusive to Qualcomm, but that hasn’t been true for at least a couple years, maybe longer.

Technically speaking, Bootcamp is an iBoot problem. Apple stopped shipping Macs with firmware UEFI which breaks 99% of generic OS installers out of the box.

Microsoft is pretty justified not wanting to support that, versus UEFI on OG Bootcamp. The majority of Linux distros don't ship image support for iBoot either.

> Apple stopped shipping Macs with firmware UEFI which breaks 99% of generic OS installers out of the box.

Did Apple ever support UEFI? I thought it was only ever EFI; no U.

Yes: https://support.apple.com/guide/security/uefi-firmware-secur...

In any case, EFI is still well-supported by OS installers. iBoot is not.

Reply on news.ycombinator.com