Lynx

still kicking since 1992
still alive (hanging-on) us
a text-only browser from 1992 that shipped a new release in 2026. mosaic is dead, netscape is dead, a dozen browsers that were going to change everything are dead, and lynx is still in every package manager, still maintained, still rendering the web as text for people and machines that need exactly that.

~ what it is ~

a browser with no images, no javascript, and no mouse. lynx renders web pages as plain text in a terminal. you move through links with the arrow keys, you press g to go to a url, you press q to leave. it was built in 1992 at the university of kansas by lou montulli, michael grobe, and charles rezac, announced on usenet on july 22 of that year. it started as a campus information system and a gopher client, and grew a proper web interface in 1993 with version 2.0.

that makes lynx older than mosaic, older than netscape, older than every browser anyone has an icon for. it watched all of them arrive and it watched most of them leave.

~ where the people went ~

lou montulli left kansas for netscape, where he became one of the people who defined the early commercial web. he invented the http cookie. netscape rose, netscape fell, the browser he helped build there has a grave on this site. the browser he left behind in kansas is still shipping. software history does not usually arrange its ironies this neatly.

maintenance passed to volunteers, and for decades now the project has been led by thomas dickey, the same person who maintains ncurses and xterm, which means a noticeable fraction of the terminal ecosystem is one man's quiet ongoing chore. lynx 2.9.3 came out on may 27, 2026. the changelog is dry. the software works.

~ who actually uses it ~

blind and low-vision users, first. a text browser feeds screen readers and braille displays cleanly, with none of the layout noise a graphical page carries. sysadmins, second. when you are ssh'd into a broken machine with no desktop and you need to read a wiki page or fetch a download link, lynx is there, because it is in every distribution's repository and it needs nothing but a terminal. developers, third, checking what a page looks like stripped of its javascript, which is roughly what a search engine crawler sees.

my own use is maybe twice a year, always on some server where nothing else is installed, and it has never once failed to do the job. there is a specific comfort in software that you can ignore for a decade and still trust completely.

~ how it survived ~

lynx never had a company, so it never had a company's death. no acquisition, no pivot, no sunset announcement with the word journey in it. it is GPL licensed, it compiles on almost anything, including systems the rest of the industry forgot, DOS, VMS, minix, amigaos. its total absence of ambition is the survival strategy. it does one narrow thing that keeps needing to be done, and the cost of keeping it alive is low enough that volunteers have carried it for over thirty years without drama.

~ why it still matters ~

every page that works in lynx is a page that works for screen readers, for crawlers, for slow connections, for the future. it is the honest mirror of the web. when a site renders as a blank screen in lynx, the site is telling you what it actually is underneath, and it is usually not flattering.

the graphical browsers that replaced it needed hundreds of engineers and lost anyway, one by one, to the next graphical browser. lynx needed a mailing list. it is still here, reachable by typing four letters into any terminal on earth.

~ leave a tribute ~

it survived. tell us how you used it. anonymous welcome.

outlived these graves: Line Mode Browser, NCSA Mosaic, Netscape Navigator

« previous  ·  random  ·  next »