[jraph]

Falkon uses QtWebEngine, which uses Blink, Google Chrome's engine.

Which is a shame, because as a KDE user, I would consider using Falkon otherwise.

It's extra painful knowing that KDE built KHTML, used by Apple to build WebKit, used by Google to build Blink…

[forgotpwd16]

Writing and maintaining a state-of-art browser engine is hard. Using an existent one is best choice unless you don't care about people actually using your browser or they're fine with accessing a part of the web.

[jraph]

> Writing and maintaining a state-of-art browser engine is hard

I know. And the KDE team would know too, having tried (and succeeded at the time! but could not keep up)

> unless you don't care about people actually using your browser

Why so dismissive?

Blink is not the only existing browser engine that works with most of the Web.

I'm not arguing for Falkon authors to build their own engine. That would be fantastic, but I understand they don't. I also understand their choice to use what Qt provides. Embedding another browser engine would be less straightforward or even outright painful / impossible (Gecko). Still, I don't want to strengthen Chrome dominance on the Web.