@aks And while we're at it, if you're using:
Brave
Opera
Opera GX
Opera Neon
Vivaldi
Edge
Epic
SRWare
Brisk
Colibri
Ungoogled Chromium
Kiwi
Yandex
Comodo Dragon
and more, then you are just using Chrome with a different skin and still contributing to Google's monopoly! Unless you are on Mac using Safari or Linux using some Linux browser, then your only choice for not using Chromium is Firefox, Firefox forks, or Tor. If you don't like this lack of choice, then stop contributing to Google's monopoly and make people develop non-Chromium browsers! Or, if you have the know-how, start work on a non-Chromium browser!
Resistance is a download away!
@daedalousilios @aks I wonder why chromium has so many different reskins while Firefox used to but no longer does. Couldn't possibly be that Mozilla has actively and deliberately worked to make Gecko useless outside of the mainline Firefox and Thunderbird codebases (wouldn't surprise me if it wasn't at google's request, given that the majority of their revenue comes from them). Not that you shouldn't still use Firefox over chrome
@daedalousilios @aks Also suspsicious that having a completely reskinned browser with extra functionality didn't require a fork at all but could be done with in-browser extensions until Mozilla mysteriously ripped it out of Firefox in 2017. Couldn't possibly be Google (who constitute more than half of Mozilla's revenue) demanding they remove features that make Firefox appealing compared to chrome
@daedalousilios
But Gecko used to be much easier to work with, until around 2015 they stopped developing or documenting all the embedding APIs and started tieing Gecko heavily into the Firefox frontend for no good reason, which killed it from being a standalone engine. They were a 600 million dollar company at that point and could certainly hire devs to maintain the embedding API.
Not strange at all that two years before Google (Mozilla's largest revenue stream both now and at the time) released Blink, the only other usable-on-the-modern-web alternative, which is easy to embed since it's a fork of WebKit (that being a hostile fork of KDE's KHTML)
@nytpu
It's probably because Chrome is written in C++ which anyone can integrate with, while Firefox is written in some weird new language that doesn't really interoperate with desktop applications , oxidation or something?
@daedalousilios @aks
@daedalousilios @aks As someone who works at Vivaldi and has contributed to heavily modify chromium both to disable Google's feature and add our own, while also on occasion helping pushing against Google on the public scene, I would like to point out that there is a significant difference between Google's dominance of the market and Chromium's dominance of the market, with the former being much more harmful than the latter.