Oldest GUI application that still runs on Windows 11

Original Article ↗ Hacker News Discussion ↗

Windows’ ability to run decades‑old GUI applications on Windows 11 prompts admiration for the stability of the Win32 API and Microsoft’s long-standing commitment to backward compatibility—often contrasted with the shorter support horizons on Linux and macOS. Commenters trade examples of very old software still functioning (from FreeCell and CD‑player apps to obscure Win32 tools), and compare that to the difficulty of running old binaries on modern Unix-like systems. The thread branches into a broader critique of modern UX trends—flat, “mobile‑first” interfaces, hidden controls, inconsistent cross‑platform toolkits—and nostalgia for the clearer, more discoverable desktop UI paradigms of the Windows 95–7 era.

Windows backward compatibility

  • Many comments praise Windows’ ability to run decades‑old Win32 apps unchanged on Windows 11, contrasting this with frequent breakage on Linux/macOS.
  • Win32 is described as an unusually stable ABI; people cite 1990s utilities, classic games, and even 3.1‑era components like ODBC dialogs still working.
  • 16‑bit support (NTVDM) is gone on 64‑bit Windows, but third‑party emulation (e.g., winvdm) and findings about possible kernel support suggest it’s a policy/effort trade‑off more than a hard impossibility.
  • Compatibility is seen as cooperative: the OS does a lot, but badly written old apps can still need patching to work well on modern systems.

Old software, games, and nostalgia

  • Examples mentioned: classic FreeCell and Solitaire, EasyToon, Orly’s Draw a Story, Solitaire’s Journey, old CD players, legacy medical/ERP systems.
  • People share emotional stories (e.g., preserving a relative’s FreeCell scores across machines) and frustrations with ad‑laden or “blinged‑out” modern replacements.
  • Some experiments show older components (e.g., CDPLAYER.EXE) partly work but clash with modern OS behaviors like automatic media handling.

Linux/BSD and other OS compatibility

  • Several argue very old unmodified Unix/X11 binaries are hard to run on modern Linux due to userland ABI drift and library changes.
  • Others counter that NetBSD and some BSDs maintain strong binary compatibility for certain 1980s/1990s platforms (SunOS, ULTRIX, etc.), though often on non‑x86 hardware.
  • Containers, static linking, and “manylinux” are cited as workarounds for Linux ABI fragmentation; the kernel itself is praised for not breaking userland.

UI/UX nostalgia and design debates

  • Strong nostalgia for Windows 95–7 (and sometimes NeXTStep) era UI: clear affordances, always‑visible menus, consistent keyboard navigation, low resource use.
  • Critiques of “flat” and “mobile‑first” design: hidden functionality, oversized controls, vanishing scrollbars, tabs in titlebars, loss of menu bars, and inconsistent cross‑app behavior.
  • Skeuomorphism vs flat design splits opinion: some see skeuomorphic buttons and textures as more usable; others note extremes (e.g., old QuickTime UI) became gimmicky or mouse‑only.
  • Ribbon vs menus: some say Ribbon improves discoverability and exposes context‑sensitive tools; others prefer classic customizable toolbars/menus, especially for expert workflows.

Native vs cross‑platform tooling

  • Debate over writing new Windows apps in raw Win32 versus higher‑level or cross‑platform frameworks (WinForms, WPF, WinUI, Avalonia, Qt, wxWidgets, JavaFX, Electron).
  • Pro‑Win32 camp cites tiny, fast, highly responsive binaries; critics note missing modern features (dark mode, HiDPI, modern text, GPU rendering) and maintenance pain.
  • Some prioritize “works anywhere” over native look; others argue cross‑platform UIs are inherently sub‑par and should match each platform’s conventions (shortcuts, accessibility, text navigation).