As most of you know, I’m one of those people striving to move as much as possible into Emacs. I’ve mostly succeeded in that except for the usual sticking point: the browser. No modern browser will run in Emacs and I’m not sure that we’d want one to. Still, it would be nice to be able to do all or most of our browsing tasks from with Emacs.
There is, of course, EWW. It does a pretty good job of displaying text and images but has no JavaScript support. Some of us consider that a feature. It turns out that most of what JavaScript does isn’t really necessary and merely gets in the way.
Joshua Blais has taken using EWW a step further and made EWW his default browswer. That means that whenever he clicks on a URL and certain other links, the link is opened in EWW or—for special links—in another application that runs in Emacs. The point is, all browser activity starts in Emacs, usually in EWW.
Of course, Emacs can’t handle every browsing task so Blais uses the & key in EWW to escape to a “normal” browser. Blais says that EWW suffices for 85–90 percent of his use cases. He has some functions to kick off Emacs apps for MP4, PDF, and other specialized links. Everything else goes to EWW. He’s added a couple of custom bindings for EWW functions he uses a lot but it’s mostly a normal EWW instance.
Blais’ experiment shows that it is possible to almost browse from within Emacs. Sites that rely on JavaScript in an essential way are not going to work of course, and there are still a lot sites that insist on JavaScript so they can enforce the delivery of ads or implement a pay wall. Blais’ method gives us a chance to consider if those sites are worth viewing.