I use #qutebrowser—and I love it from a user perspective.
But, since Microsoft announced the end of EdgeHTML, I've been wondering if I'm contributing to the browser-engine monoculture—after all, qutebrowser is, ultimately, based on Chromium. On the other hand, I'm keeping the actual browser market more diverse than if I switched to Firefox…
What do y'all think—is it better to use non-Blink browsers these days? If so, what's the best (esp. with vim keys)?
CC @the_compiler (qutebrowser dev)
@codesections @the_compiler You can use Vimium-FF with Firefox but it's not as responsive and customizable as qutebrowser.
I've not tried Vimium-FF, though I tried Tridactyl and VimVixin back before I discovered qutebrowser and, at least at the time, neither were nearly as good as qutebrowser is. But yeah, one of those might be the way to go if I decide to get away from Blink/Chromium.
@codesections @the_compiler The GTK+ browsers (Mindoro, GNOME Web, my own Odysseus, etc) are built on WebKit, so you can aid both.
I think you understand my reasoning.
Though Gecko-based browsers are few and far between. Mozilla apparently tried and failed to make it easier to embed in other UIs.
@jason @trawzified @codesections @half_cambodian_hacker_man Yes, I do think an offensive push is needed. Which is why I'm starting my Memex browser engine. (after thinking hard about the feasability of it)
But I count three projects for us (or anyone else) to rely on? WebKit's still very active.
@jason @kungtotte @kde @trawzified @codesections @half_cambodian_hacker_man Yup, the currently active "ports" I see in WebKit are:
* a self-contained one geared towards appliances
* GTK
* Mac OS
* iOS
* Windows
And the project has set up an open governance model.
@codesections @the_compiler I think firefox is the only way to go. Then again, I started with netscape, then moved to seamonkey, and on to firefox. Never was dirty rotten traitor using chrome based browser.