Mac at any scale

Original Article ↗ Hacker News Discussion ↗

Apple’s licensing limits and lack of server‑grade Mac hardware are forcing cloud providers and teams to improvise, from racking hundreds of Mac minis and MacBook Pros to virtualizing macOS within strict EULA constraints. Commenters weigh the legal gray areas, high per‑minute pricing versus buying machines outright, and operational quirks like FileVault, flaky USB/HDMI, and lithium‑ion battery risks in data centers. Several note emerging workarounds for building iOS apps without Macs at all, arguing that Apple’s stance is increasingly out of step with modern CI/CD and infrastructure practices.

Apple Licensing and VM Limits

  • Multiple comments dissect Apple’s macOS EULA:
    • Up to 2 macOS VMs per physical Mac are allowed, and only for dev/testing/server/personal use.
    • Separate clause bans using macOS VMs for “service bureau / time-sharing / similar services,” which casts doubt on selling VM access.
    • Some argue providers can comply technically (24‑hour exclusive allocation per VM/Mac) while choosing more granular billing. Others think this is wishful interpretation and likely non‑compliant.
    • Renting Macs bare-metal has a 24‑hour minimum under Apple’s terms; some providers work around this with contractual indirection (e.g., “subcontractor” framing).

Economics of Cloud Macs vs Buying Hardware

  • Many see cloud Mac pricing as “ludicrous” for steady or high‑volume CI; a $600–900 Mac mini can pay for itself in under a year given typical per‑minute rates.
  • Counterpoint: for low‑frequency use or small teams, renting can be cheaper and avoids running a mini “data center.”
  • Resale value of Mac hardware strengthens the “buy” argument; minis and laptops retain significant value.
  • Concern that hosting providers “hoard” Minis/MacBooks, exacerbating shortages and pushing up wait times.

Why MacBooks in Racks & Datacenter Risks

  • Thread notes: Mac minis and Studios would be better form factors, but supply constraints and staggered chip releases push some providers to MacBooks.
  • Debate over lithium‑ion battery density in racks:
    • Some argue data centers are already well‑equipped for battery risks, and stable temperatures plus smart charging reduce hazard.
    • Others say DC operators and insurers may object; at minimum, hosts should disclose this configuration.

Apple’s Disinterest in Servers / Enterprise

  • Widely shared view that Apple has little interest in server or enterprise offerings despite clear demand for rackable Macs or Xserve successors.
  • Some speculate Apple’s focus on high‑margin consumer devices and fab constraints makes this rational for them, even if it forces awkward setups (racked laptops, DIY racks).

Alternatives to Macs for iOS/macOS Builds

  • Several projects are mentioned (xtool, Omarchy, custom cross‑compilers) that can build and even sign iOS/macOS apps from Linux.
  • Limitations: lack of official support, early‑stage tooling, no iOS Simulator, unclear viability for large‑scale CI.
  • Thus the article’s “you can’t build iOS apps without a Mac” is challenged technically, but remains de facto true for mainstream, fully‑supported workflows.

Tooling, CI, and Code Signing

  • iOS/macOS CI is seen as harder and more fragile than Android on generic Linux runners.
  • Mixed opinions on Apple’s progress:
    • Some say code signing and CI (esp. Xcode Cloud) have improved dramatically, with Swift/SwiftUI praised.
    • Others still experience frequent signing breakage and opaque errors, and move to Xcode Cloud or specialized providers mainly to offload Apple‑specific pain.

Operations, Networking, and Distribution

  • Comments dig into practical issues: external 10GbE NICs for Macs, flaky USB/HDMI behavior, and quirks like USB NICs “disappearing” until reconfigured in macOS.
  • The provider describes:
    • Heavy reliance on MDM, SSH, KVM, and VNC for remote management.
    • Disabling sleep/auto‑update and USB restricted mode.
    • Custom peer‑to‑peer image distribution inspired by BitTorrent to speed deployment.

Apple Infrastructure and Security Critique

  • One long sub‑thread criticizes Apple’s alleged internal infra practices (use of Puppet, Jenkins, weak supply‑chain controls), though details are contested and partially unverifiable in the discussion.
  • Some argue for much stricter, immutable, VM‑per‑service architectures; others question the practicality and performance costs, asking for clearer threat models.