Emacs Is My Browser

Treating Emacs as a primary web browser promises deep integration with editing workflows and a more focused, text-centric experience, but runs headlong into the realities of today’s JavaScript-heavy, Chrome-optimized commercial web. Commenters weigh the appeal of eww, xwidget-WebKit, and other minimalist or text-only approaches—especially for documentation, automation, and low-resource machines—against practical drawbacks like broken sites, missing features, ergonomics, and potential security concerns. Underneath is a broader split between those who enjoy Emacs as a highly customized, Lisp-driven “computing environment” and those who see mainstream browsers and IDEs as more efficient for everyday use.

Compatibility of Emacs Browsing with the Modern Web

  • Emacs browsing via eww or xwidget-WebKit works well for static HTML, blogs, docs, PDFs, and Jupyter notebooks.
  • It struggles or fails on many commercial / JS-heavy sites (e.g., Google Docs, Reddit, some retail and finance sites).
  • Some report Firefox (often with JS disabled and reader mode) handles nearly everything they need; others hit increasing site breakage, especially with certain add-ons or on Linux.
  • Opinions differ on how “Chrome-only” the web really is; several say when something breaks in Firefox, it’s often just a broken site, not Firefox.

Motivations: Focus, Workflow, and Text-Centric Computing

  • A major reason to use eww is reducing distraction and “Layer 8” social UIs, treating the web as a plain information delivery channel.
  • Users value having code, notes, docs, LLM chats, scraping tools, and browser content in one text environment with shared buffers, macros, and custom commands.
  • Text-only workflows help some people (especially with attention issues) avoid GUI “menu purgatory,” mouse use, and visual overload.

Skepticism and Alternative Views

  • Critics find many “I use X unconventionally” posts unsatisfying when the main “benefit” is merely self-imposed inconvenience.
  • Some argue all touted benefits (side-by-side docs, text manipulation, AI integration) can be achieved with conventional editors, browsers, OS hotkeys, and IDE features.
  • There’s a recurring conclusion that Emacs strongly appeals to those who enjoy building a personal computing environment; others see that investment as wasted time.

Ergonomics and Keybindings

  • “Emacs pinky” concerns prompt suggestions: Evil mode (Vim-style), god-mode, remapping Caps Lock or Alt/Ctrl, and using both hands for modifiers.
  • Some prefer Emacs chords to modal editing; others find Emacs hotkeys “insane” and prefer IDE defaults.

Performance, Architecture, and Security

  • One view: single-threaded, blocking Emacs is poorly suited as a browser/WM and leads to pauses or hacks.
  • Counterpoint: async I/O, multiple Emacs processes, and modules are usually enough; lack of intra-process parallelism is seen as a design tradeoff, not fatal.
  • Concerns are raised about future “security apocalypse” from using Emacs as a browser; others dismiss this as vague fear-mongering, emphasizing risk management and the reduced attack surface without JS.

Minimalist / Text-Only Web and Tooling

  • Several long-time users browse almost entirely in text (lynx, links, w3m, eww), often without X11, treating the web as non-interactive information retrieval.
  • They argue that dropping JS and modern browsers greatly reduces tracking, ads, and surveillance-driven “interactive” behavior.
  • Tools are mentioned that render JS-heavy pages via headless browsers into text (sometimes using LLMs), or deterministically via OS scripting, to keep living in Emacs.