> Dillo is a multi-platform graphical web browser known for its speed and small footprint.
> Dillo is written in C and C++.
> Dillo is based on FLTK, the Fast Light Toolkit (statically-linked by default!).
Dillo doesn't have a JS engine. (This is a "pro" in my opinion.)
Using it the web is divided into three equivalence classes:
1) Works. (defined as, the site loads, the content is accessible and it looks more-or-less like the author intended.) As a rule such sites load lightning fast.
2) Broken but the content can still be read. Usually the site layout is messed up.
3) Broken completely. Typically a blank page, or garbage without visible content. (There is a new failure mode: sites that won't reply to browsers without server name indication (SNI https://www.cloudflare.com/learning/ssl/what-is-sni/ ) Dillo doesn't (yet) support SNI, so those sites are "broken" too. Typically these are Cloudflare-protected sites that give me a 403, but e.g. PyPI recently adopted SNI and went from category 1 to 3.)
(HN is in category 2 FWIW: you can read the content but the "bells and whistles" don't work, login, voting, etc.)
I don't really have much to add, just that A) enough of the web works that I find it useful to use dillo for my purposes, B) the web that does work with dillo is much less annoying than the "modern" web, C) it kinda sucks IMO that most of the web is junk from the POV of dillo user agent.