@justine

@amin's the #qutebrowser superfan. XD

For me, I've tried it and found it very usable for even fairly modern/intensive web sites, but the Blink (Chromium)-based backend (a sad limitation of modern Qt) keeps me from adopting it. Personal call.

For #dillo, it's never going to replace a modern web browser, but think of it as a great browser for the smol web. I can read any decent text-based page with it, even with a little bit of CSS formatting. It's far from perfect, and doesn't even pass the Acid2 test at this time. But it's a wonderful smol browser for the smol web. ;)

For every day heavy web stuff, I use #LibreWolf with the Vimium-C extension.

@rl_dane @justine

but the Blink (Chromium)-based backend (a sad limitation of modern Qt) keeps me from adopting it. Personal call.

I understand that… personally Mozilla has gone far enough off the rails that I don't think it makes a big enough difference to keep me off of Qutebrowser.

I am looking forward to the hinted possibility of Qutebrowser adding a Servo backend once that project starts making embedding more possible, though.

@amin @justine

#Mozilla has gone hilariously off the rails. By hilariously, of course, I mean incredibly tragically.

I'm still not comfortable sending a message to every site I visit that, "Yes, I am just another Chromium-based browser, feel free to make your site only work with Chrome."

...because I fought that battle 20 years ago, and we won it. I won't go back to a single company having hegemony over the web.

Riker on the Borg-trashed Enterprise, firing on every other ship because he won't go back.
Kiazi's children, their faces wet.
Shaka, when the walls fell.

@rl_dane @justine

I don't see any more value in allowing Mozilla to have a monopoly on "not being Chrome" either, though. Because that's essentially what we have.

Really, we need at least three competing completely-independent standards-compliant browser engines, ideally more. Right now we have three disgustingly-corporate browser engines.