X debut 40 years ago (1984)

Original Article ↗ Hacker News Discussion ↗

X Window System’s 40th anniversary prompts both nostalgia and technical reflection on how a 1984 MIT project became the long‑lived foundation of Unix and Linux graphical desktops. Commenters recall early hardware, modeline tweaking, X terminals, and the massive Xlib manuals, while noting X11’s stable protocol and extensibility as reasons it has endured unchanged since 1987. The conversation also contrasts X with successors like Wayland and alternative window systems, touching on missed opportunities (such as integrated audio) and how changing lab culture and cheaper personal hardware have reshaped how people encounter Unix GUIs today.

Origins, Versioning, and Naming

  • X originated in MIT’s Project Athena (1984); protocol reached X11 in 1987 and has stayed there due to an extension mechanism instead of breaking changes.
  • Comparisons to XML/SGML and Kerberos highlight that long-lived “version 1.x/5” protocols are common when extensibility is built in.
  • X is emphasized as a protocol, not an API; APIs change, but the protocol’s stability lets decades‑old clients still draw on modern servers.
  • The name came from incrementing “W”; people joke about the missing “Y” system and various failed X12/Y/Z successors.

Wayland, Apple, and X’s Obsolescence

  • Some say they’ll only be “ready” for Wayland decades from now, joking about Linux desktop timelines.
  • One view: X has been obsolete for some uses since the 1990s; Apple evaluated X for OS X and chose a different stack (Display PostScript/Quartz), citing multiple technical shortcomings.
  • A counterpoint stresses NeXT’s earlier choice and notes X outlived many competitors.
  • Wayland is seen as mature enough for ChromeOS (including its main UI now), WSL2, and automotive UIs, but some doubt it will still dominate by the time X is finally retired.

Labs, Hardware, and Early Linux Experiences

  • Many reminisce about first seeing/using X on university workstations, X terminals, and early Linux boxes (Slackware, FreeBSD) with stacks of floppies and tiny CRTs.
  • Stories highlight shared Unix labs with Sun, HP, SGI, VAX, and early Linux systems, and how that culture has largely vanished as personal laptops replaced labs.
  • Networked X terminals (thin clients) impressed people: multiple users on a single SPARC or VAX, playing Netrek/Xpilot and doing remote logins.

Protocol Design, Networking, and Audio

  • X’s network transparency and performance tricks (event shedding, zero‑round‑trip window creation) are praised; it enabled remote displays and even remote Quake.
  • Lisp (CLX) and CLU bindings are mentioned, with old compilers recovered and runnable on emulators.
  • Lack of a built‑in audio protocol is seen as a missed opportunity; attempts like NetAudio/NAS existed but never gained traction, partly due to technical flaws and lack of integration.
  • There’s tension noted between integrating services (like audio) into X/Wayland vs keeping them as separate network services.

CRT Modelines, Tapes, and Tooling

  • Configuring XFree86 modelines on CRTs was tricky; people recall warnings about potentially damaging monitors. Some report no issues, others describe real hardware risks.
  • Advanced users overclocked CRTs via custom modelines to get very high resolutions.
  • “Bring a tape for the code” sparks discussion of 9‑track and QIC cartridges, DEC tapes, and early distribution practices.
  • X predates modern VCS tools like CVS, but older systems such as SCCS were available and mentioned.

Legacy and Sentiment

  • X is repeatedly described as ancient yet still functional and surprisingly fast.
  • People recall massive Xlib manuals, steep learning curves, and a mix of frustration, admiration, and nostalgia.
  • Overall tone: respect for X’s longevity and capabilities, coupled with recognition of its warts and the complexities of moving on to successors like Wayland.