Lynx is the oldest web browser still being maintained

Hacker News Discussion ↗

Modern usability on today’s web

  • Lynx has no JavaScript, so many modern, JS-required sites are unusable (Mastodon, some wikis, many web apps).
  • Well-structured, text-focused sites often work “great”; JS-heavy or layout-complex sites are blank or broken.
  • Several commenters deliberately use Lynx (or similar) as a primary browser to avoid the “modern” web, falling back to Firefox/Chromium only when necessary.

Layout, accessibility, and “text-first” HTML

  • Biggest problem isn’t just JS but layout: long nav menus and sidebars appear before content, forcing lots of scrolling.
  • “Jump to content” links (e.g., Wikipedia) improve Lynx usability; some sites intentionally move headers to the bottom in HTML so text browsers see content first.
  • Testing with Lynx can reveal structural HTML issues (e.g., missing spaces between links, jammed dates/titles) that are hidden by CSS.
  • There’s disagreement over whether authors should care: some see Lynx-friendliness as good accessibility practice, others see text-mode as an ignorable niche.

Typical use cases

  • Low-bandwidth or expensive links (satellite at sea, hotel captive portals, 2–5 KB/s connections) where Lynx or w3m over SSH/Mosh made the web usable.
  • Server-side and terminal workflows: browsing from tmux/SSH, quick HTML previews (lynx --dump), debugging cloud apps, reading HN and docs in a terminal.
  • Email: used with mutt to view HTML mail; used to dump site link lists for analysis or as a search tool via aliases.

Alternative text browsers and headless stacks

  • Other text/TUI browsers mentioned: w3m, Links/elinks, Dillo, Edbrowse; some support limited JS or graphics-in-terminal.
  • Proposals and tools for “Lynx-like frontends over modern engines”: headless Chromium/Firefox piped into Lynx, browsh (Firefox-based), Carbonyl (Chrome-based).
  • Some imagine pairing such setups with LLMs to summarize or extract text over poor connections.

Minimalism, gopher, and philosophy of the web

  • Nostalgia and advocacy for simpler, no-JS or basic-HTML sites; some argue only regulation will curb the complexity “cartel” of major engines.
  • Gopher, Usenet, IRC are praised for efficiency on old/low-power hardware; others counter that obsolete machines lack modern security.
  • Debate over whether the web was fundamentally graphical vs text-first, and whether today’s JS-heavy, ad-driven evolution was “natural” or a choice that harmed simplicity and accessibility.