Hacker News Reader

Comment by tmikaeld | Hacker News Reader

Seems to be a nice UI around QtWebEngine which is based on WebKit or blink (chromium), with quite a solid effort through the years.

View on HN

> chromium

Are there any Google risks for being chromium-based? Honest question here.

As noted in a sibling to your comment, there's a choice between WebKit and Blink (your build allowing).

Here's QT's note addressing your concern in QtWebEngine: https://wiki.qt.io/QtWebEngine#Relationship_to_Chromium

    Auxiliary services that talk to Google platforms are stripped out

So, if Chromium turns into a bun fight with Google, the Open Source components would just fork?

I can't find a source, but I know Brave has had upstream Google issues in the past. Unfortunately, from what I've heard, Gecko is not very developer friendly, so Google is pretty much the only option.

I feel like Mozilla's decision not to prioritize support for embedding Gecko ended up being a strategic error in the long-term. Other browsers using Blink don't add directly to Chrome's market share but having it embedded everywhere means that its quirks don't end up being perceived as Chrome-specific. If five different browsers all behave the same way and the sixth one differs, then the sixth one ends up looking like the odd one out, even if the reason the other five behave the same is that they're all sharing code.

It was no strategic error. They just took the money and told the users to FO. The strategic error was having a board of directors taking decisions about a browser.

A poor decision that they continued to make with servo.

When safe browsing is enabled ( by default) it send all your browsing habit to google.