Hacker News Reader

Building on top of a framework that bundles a Chromium should result in a smaller application than building on top of a framework that bundles a WebKit. As an example, compare Vivaldi (Chromium) and Orion (WebKit).

Chromium has many more batteries included though, such as V8/Node.

View on HN

I believe the right term here is WebView, which will use the OS's native browser framework to display the app. For Windows this would be Microsoft Edge WebView2 and for Linux webkit2gtk. I do believe Qt WebEngine (or Qt WebView) might be the better option for Linux though, although I'm guessing webkit2gtk is being used because of more readily available Go bindings.

You’re wrong in your belief. We all know what a WebView is, but what is being discussed is bundling WebKit vs. bundling Chromium (like Electron does). A solution that bundles only a WebKit engine would be smaller than one that bundles a Chromium. What is your objection, specifically?

Reply on news.ycombinator.com