I see a lot of blog posts recommending EWW. Sometimes I even write about them. The common theme is something along the lines of, “No, you can’t really replace a full-fledged browser with EWW but you can do a lot and a ”real“ browser is only a keystroke away.”
In another May Emacs Carnival entry, Omar AntolĂn Camarena offers his reasons for using EWW. He agrees with the conventional wisdom that EWW isn’t a replacement for a normal browser but that it is useful in many situations and even has some advantages over your default buffer.
He believes that one of the chief advantages of EWW is that it doesn’t run JavaScript. That’s ironic, of course, because EWW’s lack of support for JavaScript is one of its most oft cited shortcomings. But Camarena says that lack is often an advantage because JavaScript is often used to load ads or a paywall or to reconfigure your display preferences often choosing low contrast colors that are hard for anyone but the young to read.
His second reason for using EWW is that it brings the power of Emacs to your Web browsing. Among the advantages he lists are:
- You can easily resize images without changing font and other sizes.
- You can read the Web site content in multiple columns using
follow-mode. - You can use
occurfor a search and keep a list of results and easily navigate among them. - You can evaluate ELISP directly in the EWW buffer and many other language as well with a bit of plumbing.
- You can use
eww-readableto eliminate a lot of the junk that comes with many Web pages.
And, as Camarena stresses, you can always escape to a normal buffer with eww-browse-with-external-browser, bound to & by default.