HN Debrief

hdiutil is deprecated in macOS 27 Golden Gate

  • Apple
  • Developer Tools
  • Programming
  • Infrastructure

The post is a complaint from a macOS developer about Apple deprecating `hdiutil`, the command-line utility used to create, inspect, mount, and otherwise manipulate disk image files on the Mac. Apple’s stated replacement is `diskutil image`, a newer subcommand under the general disk management tool. The problem is not that a replacement exists. It is that the replacement is incomplete and changes behavior in ways that break scripts and long-settled workflows. The article also uses an Apple bug report exchange to argue that nobody inside Apple seriously looked at the regression.

If your build, packaging, or support scripts touch macOS disk images, audit them now and test `diskutil image` before you are forced onto it. More broadly, treat Apple deprecations as a product risk even when the replacement exists, because the rough edges often land on automation and developer tooling first.

Discussion mood

Mostly frustrated and cynical. People were less worried that `hdiutil` will disappear tomorrow than annoyed that Apple deprecated a widely used tool before the replacement matches it, then backed that up with the usual stories about low-quality bug triage and weak support for developer workflows.

Key insights

  1. 01

    Deprecated on Apple often means frozen

    Apple deprecations often signal neglect rather than imminent removal. Examples like `xip`, `sandbox-exec`, and old `launchctl` verbs show that tools can stay in place for years if the system still depends on them or nobody has finished the migration path. That changes the practical reading of this story. The risk is stagnation and paper cuts, not necessarily a near-term hard break.

    Do not wait for a removal notice to reduce your dependency, but also do not assume you need an emergency rewrite this quarter. Plan for a long tail where the old command still works while accumulating more edge-case failures and less support.

      Attribution:
    • nrabulinski #1
    • bbatsell #1
    • dieulot #1
  2. 02

    RAM disk support already moved

    One concrete concern in the article comments was whether `hdiutil` deprecation kills RAM disks. It does not. `diskutil image attach ram://${size}m` already covers that case, which shows Apple is migrating at least some real functionality rather than simply deleting it.

    Check the specific `hdiutil` features you use instead of treating the whole tool as all-or-nothing. Some common jobs may already have a clean replacement, which lets you shrink the risky part of your surface area first.

      Attribution:
    • plorkyeran #1
  3. 03

    The bug system is optimized for closure

    The story’s weird request for an iOS sysdiagnose on a macOS bug rang true to people who have filed Apple bugs before. They said the pattern predates AI and looks like a throughput machine that re-asks reporters for diagnostics, punts reproduction work back to outsiders, and closes idle reports to keep the queue tidy. That makes the deprecation feel worse because there is no credible path to getting missing behavior fixed quickly.

    When a macOS workflow matters to revenue, do not rely on Apple feedback channels as your main mitigation plan. Build your own fallback, document repro steps internally, and assume outside bug reports may not move on your timeline.

      Attribution:
    • StilesCrisis #1 #2
    • lukeify #1
    • natbro #1
  4. 04

    Apple preserves user features more than app runtime

    Several developers drew a useful line between what Apple protects and what it does not. Old hardware features like burning DVDs, syncing ancient iPods, or using legacy peripherals can survive surprisingly long. Apps and build systems get less mercy, especially when they depend on old binaries or subtle SDK behavior that shifts during required rebuilds. That distinction explains why casual users may feel Apple is compatible enough while toolsmiths feel constantly whipsawed.

    If you build for macOS, separate "user-visible feature still works" from "our software stack is safe." Test SDK updates, binary compatibility, and automation scripts as their own maintenance stream instead of inferring safety from hardware support.

      Attribution:
    • cosmic_cheese #1 #2
    • II2II #1
    • mrtesthah #1
  5. 05

    Disk images are not just disks

    The replacement story is weaker than it first sounds because `diskutil image` only covers part of `hdiutil`’s job. Commenters pointed to cases like checking whether an image is encrypted, where `hdiutil` exposes script-friendly commands and `diskutil image info` can trigger a password prompt that is awkward or wrong for automation. The issue is not nostalgia for an old binary. It is loss of non-interactive control over image metadata and edge cases.

    Review your CI and installer tooling for any use of image inspection, encryption checks, or other non-interactive metadata operations. Those are the spots most likely to break even if basic attach and detach operations migrate cleanly.

      Attribution:
    • KlayLay #1
    • doodlesdev #1

Against the grain

  1. 01

    This is not a sudden compatibility collapse

    Apple has been moving functionality toward `diskutil` for years, and some people pushed back on the idea that this deprecation proves Apple no longer cares about compatibility. They pointed to working DVD burning, old iPods, AirPort Express gear, and long-lived source compatibility for old Objective-C and AppKit projects. That does not excuse an incomplete migration, but it does argue against treating the announcement as evidence of wholesale platform abandonment.

    Avoid turning one bad migration into a blanket platform thesis. For planning, separate real breakage in your own workflows from the broader claim that macOS compatibility is universally getting worse.

      Attribution:
    • detourdog #1
    • II2II #1
    • cosmic_cheese #1
  2. 02

    Other platforms are not clearly better here

    When people compared Apple’s support window to Windows and Linux, the answers were messier than the usual "Apple bad, others good" line. Windows still drops machines for policy reasons like Windows 11 requirements. Linux keeps old hardware usable, but long-term app compatibility is uneven, especially for commercial and closed-source software. One commenter even pointed to XLD as proof that a Mac app can target a very wide span of macOS releases if the developer chooses to do the work.

    If you are choosing a desktop platform for longevity, compare hardware support, browser support, packaging burden, and commercial app availability separately. The headline compatibility story differs depending on whether your pain is old hardware, old binaries, or third-party app support.

      Attribution:
    • pudgywalsh #1
    • bigyabai #1
    • mschuster91 #1
    • doodlesdev #1
    • jtbayly #1
    • cosmic_cheese #1

In plain english

AppKit ↩
The macOS user interface framework within Cocoa for building desktop applications.
disk image ↩
A file that contains the contents and structure of a storage volume, often used on macOS for software distribution as `.dmg` files.
diskutil ↩
A macOS command-line tool for managing disks, volumes, and some disk image operations.
Feedback ↩
Apple’s external feedback and bug-reporting system for developers and beta users.
hdiutil ↩
A macOS command-line tool for creating, mounting, converting, inspecting, and managing disk image files.
launchctl ↩
A macOS command-line tool for managing system and user services controlled by `launchd`.
Objective-C ↩
A programming language long used for native Apple app development before Swift became dominant.
sandbox-exec ↩
A deprecated macOS command-line tool for running a process inside Apple’s sandboxing system with a custom policy.
SDK ↩
Software Development Kit, a bundle of tools and code libraries developers use to build apps.
sysdiagnose ↩
A large Apple diagnostic bundle that collects system logs and debugging information for troubleshooting.
xip ↩
An Apple archive format used for signed software distribution, including Xcode downloads.
XLD ↩
X Lossless Decoder, a macOS audio tool cited as an example of a single app binary supporting a very wide range of Mac architectures and OS versions.

Reference links

Projects and code references

  • mio Windows AFD implementation
    Referenced as an example of production software relying on an undocumented Windows interface that has become effectively stable.
  • X Lossless Decoder (XLD)
    Cited as an example of a Mac app that supports a very broad range of macOS versions and CPU architectures in one binary.

Legacy software examples

  • F-Script on Macintosh Repository
    Used as an example of older Mac software and capabilities that became hard or impossible to preserve under newer platform and security changes.