Hasty Briefsbeta

History of the browser user-agent string (2008)

10 days ago
  • #web browsers
  • #history
  • #user agent
  • NCSA Mosaic was the first browser to display images with text, leading to early web excitement.
  • Netscape, initially named Mozilla (Mosaic Killer), introduced frames, prompting user agent sniffing for compatibility.
  • Microsoft created Internet Explorer to compete with Netscape, leading to the first browser war.
  • Netscape's decline led to the birth of Mozilla and the Gecko rendering engine, which powered Firefox.
  • Browser user agent strings became complex as browsers impersonated each other for compatibility.
  • Opera introduced user-selectable user agent strings to mimic other browsers.
  • Apple's Safari used KHTML, leading to the WebKit fork and further user agent complexity.
  • Google Chrome adopted WebKit, adding to the confusion by mimicking Safari's user agent.
  • User agent strings became a mess, with browsers pretending to be others, making them nearly useless.
  • The article humorously critiques the chaotic state of browser user agent strings and suggests simplification.