Why you should NEVER use a MAC for Game Dev

Summary (Game Dev on macOS vs Windows)

Context / Background

• The speaker is a long-time Apple user and previously worked as a full-time game developer on an iMac.
• They note that early Unity versions supported Mac, and that Mac wasn’t always viewed as a poor choice for game development.
• Around 2010, more PC/Valve titles were ported to Mac/Linux (e.g., Portal 2, Left 4 Dead / Left 4 Dead 2), improving the platform’s viability—especially for Unity-based indie development.

Key Historical Feature: Dual-Boot via Boot Camp

• Older Intel-based Macs supported dual booting Windows using Apple’s Boot Camp.
• Boot Camp reportedly made it relatively straightforward to install Windows plus the necessary Mac drivers.
• This enabled a practical workflow:
  • Develop on macOS
  • Reboot into Windows
  • Test Windows-specific behavior (including expectations around DirectX)

Main Technical Complaint Today: Apple Silicon + Loss of Boot Camp

• The speaker claims that on modern Macs using Apple-designed CPU/GPU chips (Apple Silicon), Boot Camp is no longer available.
• They present this as the biggest blocker for macOS as a game dev platform, because without easy dual-boot testing, validating Windows-targeted builds becomes harder.

Graphics API Constraint: Metal vs DirectX

• They argue that macOS development effectively forces the use of Apple’s Metal graphics API, which they describe as:
  • More strict/different than DirectX
  • Potentially more time-consuming, especially for tasks like building your own shaders
• They also warn about a practical risk: using complex third-party assets not designed for Metal can leave developers with a large compatibility/code-fix burden.

Testing Alternatives and Limitations

• Separate Windows PC: suggested as the likely workaround to test on Windows, implying additional cost and effort.
• Virtual machines (VMs): mentioned but dismissed.
  • They claim VM solutions (e.g., Parallels or free VM software) often lack proper GPU acceleration
  • They report performance is so poor it becomes impractical for game testing (described as “less than 1 FPS”)

Tooling / IDE Comments

• They previously used MonoDevelop, but said it became buggy and stagnant.
• They mention Visual Studio for Mac as a replacement, noting that Microsoft software “never really worked great” on Mac and felt less “snappy.”
• They also note that Rider is available on Mac, though they haven’t personally used it to judge quality.

Contradictory Positives About Mac Hardware

• They praise modern Mac performance:
  • Unity “runs great”
  • M1/MacBooks are described as fast, efficient, and long-lasting on battery
  • They claim macOS hardware can be nearly as fast as high-end desktop CPU performance for many development tasks
• Despite this, they maintain they wouldn’t switch back to Mac as their primary game dev platform due to testing/workflow constraints.

General Review-Style Conclusion

• The speaker emphasizes a tradeoff:
  • Performance + battery life on MacBooks are excellent
  • But workflow/testing challenges, graphics API differences, and lack of dual-boot make macOS a poor primary platform for game development when targeting Windows

Outro / Current Project

• They mention preparing for the release of an upcoming project, “City of Springs,” expected early next week.

Main speakers / sources

• Main speaker: A single YouTube creator/speaker (no name provided in the subtitles).
• Referenced technologies/products: Unity, Apple macOS/Metal, Windows/DirectX, Boot Camp, Parallels, MonoDevelop, Visual Studio for Mac, JetBrains Rider.