The split is real, but the framing is wrong for architects

Wired’s Luke Larsen drew a clean line between Apple’s two MacBook tiers this week: the MacBook Neo (the lower-cost option, carrying what Larsen calls “too many compromises” for full-time professional use) and the MacBook Air (the daily-driver). The price gap is $500 USD — roughly CHF 450 at current exchange rates, before Swiss VAT. That delta is not the interesting number. The interesting number is zero: as in, zero native macOS versions of Autodesk Revit.

←TODAY: Apple Silicon M-series chips run Rhino 8 natively, ArchiCAD 27 natively, and Vectorworks 2025 natively — but Revit requires Parallels, a Windows licence, or a cloud BIM client.
→3012: In the Zurich-3012 framing, the device is infrastructure, not identity — what matters is which data topology it can join at the site boundary.
Fulcrum: The MacBook question for AEC is not Air vs. Neo; it is whether your BIM stack has left the Win32 dependency behind.

Here is the system map Larsen’s consumer framing skips. Apple Silicon (M-series, shipping since late 2020) collapsed the performance gap between Apple’s laptop tiers dramatically. The “Air class” chip in the MacBook Air is not a stripped-down chip — it is the same die, with thermal constraints removed by the fan in higher-end models. For sustained CPU loads — think a Grasshopper solver running overnight or a Enscape real-time render bake — the fanless design of the Air will throttle before the Pro or the Neo’s thermal ceiling (assuming the Neo carries active cooling; Larsen’s piece confirms compromises but the excerpt does not publish a full spec sheet, and the “MacBook Neo” name is not yet confirmed in Apple’s standard product history — treat this comparison as directionally sound but verify availability before purchasing).

The bottleneck for an AEC professional is not single-core burst. It is sustained multi-core throughput under load, unified memory ceiling, and — critically — the software compatibility layer. Vectorworks and ArchiCAD ship native Apple Silicon builds. Revit does not. Running Revit on a MacBook via Parallels Desktop 20 works, but it introduces a virtualisation tax on RAM (you are splitting unified memory between macOS and a Windows VM) and a storage overhead that punishes the base 256 GB SSD configurations both devices offer at entry price. For a BIM coordinator doing full-model coordination in Revit, the $500 question is almost beside the point — the real cost is the Parallels licence (~CHF 130/year) plus a Windows licence (~CHF 150 OEM), added to whichever MacBook you choose.

Larsen’s actual decision framework — full-time professional use goes Air, secondary/student device can go Neo — maps onto AEC roles more usefully than it might seem. A junior drafter whose firm issues a Windows workstation at the desk but needs a portable device for site visits, client presentations, and PDF markups? The Neo’s compromises probably do not touch their workflow. A project architect running ArchiCAD as their primary authoring tool, no Windows VM required, on the road three days a week? The Air’s thermal headroom and display quality earn the premium. A BIM manager coordinating IFC federated models in Solibri and running BCF workflows? Get the RAM configuration right — 16 GB unified memory is the floor, 24 GB is the sensible spec — and the chassis tier matters less than you think.

Atelier: Before your firm’s next hardware refresh cycle, map your software stack against Apple Silicon compatibility using the Does It ARM? database and Autodesk’s own macOS compatibility matrix. If Revit is in the critical path, budget the virtualisation overhead into total cost of ownership — not just the sticker price delta between two MacBook tiers.

The move: pull up your firm’s BEP or IT procurement policy and find the line that specifies OS. If it still reads “Windows required” as a blanket rule, that rule was probably written before M-series chips shipped. Challenge it with data — specifically, which tools in your stack have native Apple Silicon builds today (Rhino 8, ArchiCAD 27, Vectorworks 2025, Solibri) versus which remain Win32-dependent (Revit, AutoCAD MEP). That audit, not a Wired buying guide, is the input your next hardware decision actually needs.

Source: Wired