Show HN: OS X Mavericks Forever

Scope of the Project / “Show HN” Debate

  • Some argue this isn’t a typical “Show HN” because it targets a narrow slice of old hardware, but others say that’s fine: the guide, custom tools (Aqua Proxy, plugins, patched widgets), and detailed instructions are substantial “to show.”
  • Several commenters thank the author, noting they’ve actually used the guide to revive old Macs.

Why Mavericks? Aesthetics, UX, and Era

  • Many praise OS X 10.9 as a visual and UX high point: last broadly “Aqua-ish,” fast, and still feeling like a “real computer” rather than an appliance.
  • Others prefer Snow Leopard, Tiger, El Capitan, or Mojave as their personal “peak Mac,” but generally agree the modern iOS‑style design, margins, and iconography are regressions.
  • There’s nostalgia for old QuickTime, Dashboard widgets, colored sidebar icons, and “Quake-style” drop‑down terminals/Finders.

Installation, Hardware, and Recovery Quirks

  • Discussion about which Macs can run Mavericks (roughly 2008–2014) and oddities in macOS Recovery: different key combos (Cmd+R, Opt‑Cmd‑R, Shift‑Opt‑Cmd‑R) yield different target versions; firmware level also matters.
  • Some use older releases like Catalina or High Sierra on unsupported hardware as a compromise between age and usability.

Security, Browsers, and Networking Workarounds

  • Strong concern about running a 9‑year‑unpatched OS on the internet: attack surface, sensitive data exfiltration, and outdated SSL/TLS.
  • Workarounds:
    • Modern browsers backported to legacy macOS (e.g., Firefox forks, Chromium Legacy).
    • HTTPS proxy (Aqua Proxy) to offload TLS to a modern stack.
    • Native VPN protocols vs third‑party VPN apps that bypass proxies.
    • Running modern browsers in VMs or on another machine and remoting in.
  • Some think this is still “insane” for daily‑driver use; others accept the risk with backups and a limited threat model.

Hackability vs Lock‑Down

  • Mavericks is praised for being easy to tinker with: deletable stock apps, SIMBL plugins, Objective‑C method swizzling, hex‑patching system libraries, and no SIP/SSV.
  • Counterpoint: immutable or locked‑down systems (SIP, signed system volumes, Linux images like Bazzite/NixOS) make it much harder for users to brick machines and easier to say “just try things.”
  • Long sub‑thread debates tradeoffs: freedom vs safety, admins vs normal users, and whether SIP should be easy to disable.

Alternatives: Linux/BSD, Hackintosh, and Re‑creations

  • Several commenters say this level of effort to cling to Mavericks should instead go into Linux/BSD desktops or GNUstep/NeXT‑style systems; some report being very happy on modern Linux (e.g., Bazzite, KDE).
  • Others feel Linux/Windows still trail macOS on consistency, input feel, and UI polish despite progress.
  • Projects like helloSystem, ravynOS, NEXTSPACE, and GSDE are mentioned as attempts to recreate classic Mac/NeXT UX, but seen as immature or skin‑deep so far.

Sentiment About Apple’s Direction

  • Strong thread of discontent: iOS‑ification, locked‑down design, nagging dialogs, hardware that isn’t user‑serviceable, and focus on services/ads/cloud.
  • A minority argue macOS keeps getting better: world‑class dev tools, Apple Silicon performance, and that restrictions rarely impede serious work.