98.css

Original Article ↗ Hacker News Discussion ↗

A pure-CSS library that recreates the Windows 98 look-and-feel is sparking nostalgia and admiration for its pixel-accurate bevels, gradients and system font work, all achieved without JavaScript. Commenters trade links to a broader ecosystem of retro UI frameworks (from Win95 and XP to NES and PS1), debate the usability of classic elements like multi-row tabs and disabled buttons versus today’s flat, minimalist design, and note how such projects often double as painstaking labors of love or even burnout-recovery hobbies. Some also highlight practical gaps—like missing scripting for interactive components—while still seeing these vintage-style toolkits as a refreshing alternative to modern, visually sparse interfaces.

Retro CSS and UI Theme Ecosystem

  • Thread collects many retro CSS/UI libraries: Windows 95/98/XP/7/10, PS1, NES/SNES, Geocities, Counter-Strike 1.6, classic Mac/System 7/CDE, The Sims, Winamp-style, C64, TUIs, “after dark” themes, etc.
  • Also references desktop themes that make Linux/XFCE look like old Windows versions, and people wish for similar themes on KDE and for classic macOS/OS X.
  • Some link to broader “classic stylesheets” collections that organize multiple vintage styles in one place.

Implementation Quality and Technical Details

  • Many praise 98.css for being pure CSS, with clever border/box-shadow tricks and very close, often “pixel-perfect,” fidelity to Windows 98.
  • Others nitpick: slightly off spacing, fonts (MS Sans Serif accuracy), missing or imperfect components (dropdowns, group boxes, checkboxes/radios, some tab behavior).
  • Browser limitations (e.g., select styling, mobile tab behavior) are noted; tabs on the homepage intentionally lack JS wiring.

Nostalgia, Aesthetics, and Flat Design Backlash

  • Strong nostalgia: people report unexpected happiness and vivid memories of childhood computing, games, and family routines.
  • Several argue old GUIs (Win98, XP, 2000, System 7, Windows 7) are clearer and more pleasant than modern flat UIs, which are seen as bland, over-minimal, and less usable.
  • Others counter that some old patterns (multi-row tabs, certain aesthetics) were confusing or ugly and shouldn’t be resurrected.

Usability Patterns: Tabs, Disabled Controls, and Help

  • Debate over multi-row tabs:
    • Pro: better discoverability than tiny or scrollable modern tabs.
    • Con: rows reordering after click harms orientation and wastes vertical space.
  • Long subthread on disabled vs hidden buttons:
    • Some want always-visible, greyed-out controls with clear explanations (tooltips, “?” icons).
    • Others support hiding controls when they truly never apply.
  • Multiple commenters lament the disappearance of hover help, question-mark help buttons, and clear explanations.

Use Cases, Process, and Limitations

  • Several people have wrapped personal sites, games, and apps in 98.css or related libraries, praising ease of extension.
  • The project is described as a burnout-recovery hobby; maintenance is now mostly vetting and delegating pull requests.
  • One maintainer of a related theme notes how grueling pixel-perfect work is, doubts current AI is helpful for this, and emphasizes manual, taste-driven effort.
  • Some users report visual issues on their setups (fonts, animation speed) and argue that historically accurate UIs aren’t necessarily good modern UX.