Yeah…; heh, discovered some things this afternoon. Neither browser was able to load Google without crashing the tab (which, I dunno, could – maybe – motivate me to kick the habit?).

Luakit, on my distro, is v2.3.3 and I tried building to v2.4.0 but the built executive kept saying 2.3.3 for its version. I suspect this is probably more my fault, though.

Why haven’t I tried Qute?

I dunno! Heh, I feel like it’s relatively popular but I’ve also been snooping around the minimal browser space since Uzbl so maybe my perception’s off.

The biggest reason you may not have is it is based on Chromium. At the time I discovered it, the dev.'s reason was due to security issues in WebKit, at the time, but that was also 5–9 years ago so that may not be a concern, anymore.

It’s also built with QT; I generally use GTK so it’s my one gripe but I know it doesn’t bother everyone.

And it’s built on Python (I know that bothers some); but those are the only things I can think of.

It uses the same default layout that Uzbl inspired in vimprobable, dwb, jumanji, vimb, and Luakit so that’ll probably be familiar. Vim bindings out of the box (which I feel like Uzbl also inspired in all the aforementioned browsers).

I feel like it’s the most stable of the bunch, for the most part (which is probably why I keep going back to it). It can be resource heavy but the customizability and fairly stable performance is generally pretty good.

And it got support for uBlock Origin (I’m sure there’s a generic name but I’m afraid I don’t know it) style adblock lists recently with the help of Python’s adblock library (I hadn’t realized Luakit and Nyxt had support for that until now and it was always by major con, with Qutebrowser).

Right now, there’s a Wayland display issue in suffering with but that’s QT’s fault and isn’t present on v6.8 (but my distro’s still at 6.7.2…); so that might not even be an issue, for you.