|
| ▲ | thayne 5 days ago | parent | next [-] |
| > Firefox on Linux (usually). No, linux is usually webkit (which is also what safari is based on). Both Gtk and Qt have webkit-based widgets. I'm not aware of a gecko based webview for desktop. Unfortunately, Firefox's technology is even more poorly suited for embedding than chromium's. |
| |
| ▲ | Klonoar 5 days ago | parent [-] | | WebkitGTK has notoriously lagged behind Webkit on other platforms. |
|
|
| ▲ | yoav 5 days ago | parent | prev | next [-] |
| The number 1 request I get from people is to add the ability to optionally bundle chromium. I personally prefer the system webview because you don’t have to rush update your app for every chromium security update. And on the web making things cross browser is a normal part of the job and instinct imo. But there are a ton of early startups that only have bandwidth to support chrome/chromium in their complex webapps and want a quick way to port their web app to desktop app. For them taking on the security burden and increasing bundle size is a good tradeoff to getting that consistency. Luckily electrobun has a custom zig bsdiff implementation that generates update diffs as small as 4KB and self extracting executable that uses zstd so at least the file size is less relevant of a concern compared to electron. |
| |
| ▲ | lolinder 5 days ago | parent | next [-] | | > you don’t have to rush update your app for every chromium security update I'm interested to hear more about this—if you're using security-sensitive features in a WebView, aren't you then at the mercy of the OS to patch them whenever they see fit? And if you're not using features that have security implications, why do you need the latest version of Chromium at all times? | |
| ▲ | littlestymaar 5 days ago | parent | prev [-] | | > But there are a ton of early startups that only have bandwidth to support chrome/chromium in their complex webapps and want a quick way to port their web app to desktop app. Ugh! People writing web apps without supporting anything else than Chrome should burn in hell. (And that's a pretty useless decision anyway since “supporting chrome” really means supporting two engines: Chromium and WebKit, because Chrome on iOS uses WebKit internally …) | | |
|
|
| ▲ | ericwood 4 days ago | parent | prev [-] |
| These days it's really not bad, and it's even easier than shipping a normal web app, where there's a potentially unbounded number of browsers consuming it. Knowing exactly which clients to develop for is a luxury. |
