3 ms·
At the moment, realistically using WebView2 requires shipping a WebView2 Runtime, either a fixed version or a bootstrapper. That's still over a hundred MB. I
by thrower123 5y ago
At the moment, realistically using WebView2 requires shipping a WebView2 Runtime, either a fixed version or a bootstrapper. That's still over a hundred MB. I don't quite understand why that isn't being included with Edgeium, maybe it will be there in the future, but as of now, having Edge installed is no guarantee that any software trying to use WebView2 will work.
I've got too many scars from needing to ship shared Microsoft runtimes in the past to be entirely happy about this current situation.
- wila 5y agoI've got a lot of scars from MS... but the bootstrapper is 1.7MB. It will then pull in WebView2. WebView2 btw is awesome (I've spent a lot of time with it already, see my profile if you want to know why)
- devwastaken 5y agoWebview is not a replacement. Webviews for GUIs is the worst of all worlds. You're packaging up two separate event based runtimes, chromium and node, and have no ability to interface with V8, meaning youre actually losing significant performance by having to serialize/deserislize data from node, to the browsers window, then deserislized on message in the browsers packaged JS engine. It makes no sense to treat your desktop GUIs as closed sandboxes, what's the threat model? Electron is not simply chromium, it has a bunch of optimizations, fixes, and prebundled functionality.
- mrpippy 5y agoThis entire thread is about which webview to use as an actual web view in an otherwise native application, not trying to use them as apps
- WorldMaker 5y agoShipping WebView2 runtime "in-box" in Windows is supposed to start with Windows 10 21H2 and Windows 11. I believe soon after both release (Chromium) Edge will also start shipping it by default down to previous Windows 10 versions still in security support.