Running macOS on an iPad requires a jailbreak and a hypervisor, which are not available on modern iPads. The process involves transplanting macOS frameworks into iOS binaries and writing shims for missing APIs. The speaker discusses the challenges of finding compatible iPads, such as the M1 iPad Pro, M1 iPad Air, and M2 iPad Pro, which cannot be running anything newer than iPadOS 16.3.1. Finding these iPads requires buying new-old-stock, which can be expensive and difficult to verify. The potential risks include security vulnerabilities and performance issues. The speaker notes that instructions run directly on the M2 chip, which can lead to performance drops of up to 50% in multi-core tasks.

The speaker notes that while running macOS on an iPad is a cool experience, it is inherently limited and may not be the best move for hybridizing the two operating systems. This is because even with improvements, the performance loss is significant, and the experience is not as seamless as desired. The speaker suggests that Apple should allow certain Mac apps to run natively on iPadOS, providing access to Mac-class foundations while keeping the iPad's simplicity intact.

The article suggests that allowing certain Mac apps to run as iPad apps would provide access to Mac-class foundations while maintaining the iPad's simplicity and the App Store experience. However, running macOS on an iPad is currently limited to a virtual machine setup, which requires a jailbreak and a hypervisor, making it impractical for most users.

Recording map. Duration 23:00. 00:24 — IPad Running macOS: Challenges and Risks. Topic markers are not factual verification.
ClipCast.News recording map · timestamps derived from the original recording.