EWW rendering a typical documentation page inside Emacs, illustrating the text‑first browsing experience.
*Joshua Blais reports that Emacs' built‑in EWW now handles 85‑90% of his daily web tasks, relegating modern browsers to a 5‑10% fallback. The shift reflects a push against distraction‑heavy front‑ends and big‑tech lock‑ins.*
Joshua Blais, a long‑time Emacs devotee, has turned the editor into his primary web client. After weeks of testing, he claims EWW now satisfies roughly 85‑90% of his browsing requirements, even on sites saturated with JavaScript. The remaining 5‑10% of interactions—typically video streams or complex social feeds—still trigger a fallback to Chromium or Firefox. Blais’ motivation is stark: modern browsers invite distraction, while Emacs forces a disciplined, text‑first approach. By abandoning the glossy front‑ends of platforms like Discord and Twitter, he aims to reclaim the internet’s original purpose as a neutral information conduit.
Blais finds EWW usable for about 85‑90% of typical web activities, even on JavaScript‑heavy sites. He cites its built‑in reader mode (R) that strips headers and footers, mirroring Firefox’s reader view. When a page fails to render, he falls back to Chromium or Firefox via the ampersand shortcut. The remaining 5‑10% of cases—such as YouTube videos or complex social feeds—still require a modern browser. The trade‑off is a drastic reduction in distraction and a tighter grip on what he consumes online.
Blais configures EWW with a personal Searx instance as the default search engine, ensuring privacy‑respecting results. He maps B to back, U to yank the URL, D to download images, and a to bookmark. Media links (YouTube, Vimeo, Twitch, .mp4) launch in mpv via a custom handler, while PDFs open in Emacs’ pdf‑tools after a temporary download. Gopher and Gemini URLs are routed to elpher, the protocol‑specific EWW. Visual tweaks include a 100‑character width, a maximum image size of 800×600, and disabled fonts for a cleaner layout.
He argues that modern front‑ends act as “Layer 8” barriers, funneling users into endless recommendation loops. By stripping away JavaScript‑driven widgets, he avoids the “rabbit holes” that consume his day. The result is higher signal‑to‑noise when looking up documentation, reading blogs, or performing quick searches. He notes that the internet is a delivery mechanism, not a captive audience, and that reverting to a 1999‑style browsing experience restores that perspective.
Blais has redirected all URL functions to EWW, making it the first checkpoint for any web interaction. This forces a deliberate decision before opening a fallback browser. He reports that the workflow supports quick searches, documentation review, and blog reading without logging into platforms or handling banking portals. While not a universal solution, the setup demonstrates that a text‑centric environment can handle the majority of everyday web needs, challenging the assumption that a heavyweight GUI browser is mandatory.
He reports that EWW covers about 85‑90% of his daily web use cases.
YouTube, Vimeo, Twitch, and any .mp4 links are set to launch in mpv.
Pressing & opens the page in his default modern browser, typically Chromium or Firefox.
Blais’ experiment shows that a minimalist, editor‑centric browser can reclaim productivity and privacy for users willing to trade flash for focus. As more developers adopt similar configurations, the pressure on big‑tech ecosystems to justify their attention‑grabbing designs may increase. Whether Emacs becomes a mainstream alternative or remains a niche tool, its success underscores a growing appetite for tools that prioritize signal over spectacle.
Sources: Hacker News – Emacs Is My Browser (https://joshblais.com/blog/emacs-as-my-browser/)