Qt WebEngine uses code from the Chromium project. However, it is not containing all of Chrome/Chromium:
Binary files are stripped out
Auxiliary services that talk to Google platforms are stripped out,
Source
While that’s one of the reasons I don’t want to use chromium, it’s not actually the main reason, if so I’d just use Ungoogled Chromium. I just want more web engines, and I dont want google to monopolise the internet.
It is super hard to create a new web engine, especially when one company is influencing the web standards and most web developers are only testing against that because of market share. This is why we ended up with four active web engines. In alphabetical order: Blink, Gecko, Goanna, WebKit. Obviously some are related: WebKit started out as the fork of KDE’s KHTML and Blink is the fork of WebKit. Goanna is the fork of the Unified XUL Platform that was forked from Mozilla’s Gecko.
Qt WebEngine uses code from the Chromium project. However, it is not containing all of Chrome/Chromium: Binary files are stripped out Auxiliary services that talk to Google platforms are stripped out, Source
While that’s one of the reasons I don’t want to use chromium, it’s not actually the main reason, if so I’d just use Ungoogled Chromium. I just want more web engines, and I dont want google to monopolise the internet.
It is super hard to create a new web engine, especially when one company is influencing the web standards and most web developers are only testing against that because of market share. This is why we ended up with four active web engines. In alphabetical order: Blink, Gecko, Goanna, WebKit. Obviously some are related: WebKit started out as the fork of KDE’s KHTML and Blink is the fork of WebKit. Goanna is the fork of the Unified XUL Platform that was forked from Mozilla’s Gecko.