Tour of new custom M1 macOS runners racks with Christina Warren [video]

Original Article ↗ Hacker News Discussion ↗

Custom data-center racks built from gutted M1 Mac minis for GitHub Actions spark debate over Apple’s refusal to offer server-grade Apple Silicon and the wastefulness of “shucking” consumer hardware at scale. Commenters weigh technical trade-offs such as density, cooling, power delivery, and macOS licensing against alternatives like AWS Mac instances, Hackintoshes, or Asahi Linux, while also critiquing Apple’s environmental claims and lack of support for large-scale macOS CI workflows. Many see a clear demand for official rackable Macs or cloud offerings, but doubt Apple will re-enter the server market despite the evident need from iOS and macOS development pipelines.

Custom M1 rack design & density

  • Many are surprised GitHub “shucks” complete Mac minis for the racks; seen as reminiscent of buying whole products just for a part.
  • Some think the density is underwhelming (≈60 minis per 42–48U), noting commercial shelves/rackmounts can match or beat it with intact minis.
  • Others argue the design is “pretty dense” given Apple offers no native server form factor, and emphasize benefits in:
    • Per‑sled power (A/B feeds), lights‑out management, and isolation.
    • Easy hot‑swap/maintenance by pulling a single sled.
  • Thunderbolt is used as an “extended motherboard” for external NIC/management; details in the video are sparse.

Waste, e‑waste, and Apple’s responsibilities

  • Many see the gutting of minis and discarded cases as wasteful, in tension with Apple’s public environmental messaging.
  • Some counter that parts may be resold or recycled, but others note shipping and handling extra parts is still waste.
  • A recurring wish: Apple should sell bare boards or purpose‑built Mac server blades to avoid this.

macOS licensing, Hackintosh, and legal boundaries

  • Some wonder if macOS licensing could be sidestepped (e.g., by jurisdiction shopping or pairing dead Macs with generic servers), but others note:
    • ARM Macs have effectively killed practical Hackintoshes.
    • For CI/testing, running on unsupported hardware/virtualization layers is unattractive, especially for iOS/macOS builds.

Apple, servers, and cloud ambitions

  • Debate over whether Apple should or will re‑enter servers:
    • Pro: M‑series efficiency, growing services business, internal need for Mac CI, and potential power savings.
    • Con: prior Xserve failure, Apple’s consumer focus, limited TSMC capacity, weak internal cloud stack, and low margins in IaaS.
  • Some suggest Apple could offer Mac IaaS or license chips/OS, but others argue it doesn’t align with Apple’s priorities or economics.

Developer experience & Mac CI

  • Multiple comments describe iOS/macOS CI as painful: need for physical Macs, licensing limits on virtualization, brittle app review, and opaque tooling.
  • Hosted Mac CI is seen as expensive and capacity‑constrained; some rent minis from third parties or self‑host.
  • Alternatives like packaging Electron/JVM apps from Linux are mentioned to avoid Mac build farms where possible.

Reactions to the video

  • Many found the video shallow, marketing‑heavy, and lacking technical detail (orchestration, networking design, storage, virtualization).
  • Some defend the presenters’ expertise, arguing the format, not the individuals, constrained depth; there’s extended debate around accent, tone, and bias.