fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

codesections

I use —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.

@trawzified @the_compiler

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.

@half_cambodian_hacker_man @trawzified @alcinnz

@codesections


I mostly use Qutebrowser for my main browser and occasionally Falkon. Both are Qtwebengine based.

I have at some point tried most if not all of the browsers out there available for Linux.

I think my choices are probably the sanest available in respect they are sanitized from their chromium base.

The sad fact is that unless some one creates a new backend renderer or does somthing really freaking cool with the NetSurf backend we will - for the time being - rely on one of 2 projects to provide the engines for all our browsers. (The Chromium projects and Mozilla).

@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.

@kungtotte @alcinnz

@half_cambodian_hacker_man @codesections @trawzified


Ok there is WebKit, iirc the development of which is mostly driven by Apple for safari andthe appstore

WebKit at one became very splintered and confusing at one point, with various forks / versions becoming listed as insecure

I think its WebKit2gtk that is current/secure

What I find quite interesing is that qtwebengine has its roots in the chromium projects (blink) which was forked from WebKit which originated when Apple used the code for KHTML, so thank you @kde for providing the seed

@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.