6 ms·
But why would the system webview be less resource hungry? If it runs in an own process instance, the only memory you safe is (maybe) the executable code (i.e. m
by albertzeyer 6y ago
But why would the system webview be less resource hungry? If it runs in an own process instance, the only memory you safe is (maybe) the executable code (i.e. maybe 100MB max).
Or you would need some common runtime which is shared across the OS, and somehow use IPC to it. Then you can potentially save some more memory. But I don't think this exists. And I'm also not sure how much you really would save.
The advantage of using the system webview is that you can update this component, in case there are any vulnerabilities or so.
- OskarS 6y agoDynamically loaded system libraries use shared memory. You can load it once for the entire system.
- albertzeyer 6y agoThat's what I mean by executable code. But that is only really minor (<100MB or so) compared to the remaining resource usage.
- OskarS 6y agoAh, sorry, I missed that in your comment.
- sophiebits 6y agoThey’re not inherently more efficient (other than the reduced application size), but Safari and Edge are both more resource-efficient than Chrome.
- deleted 6y ago[deleted]
- cozzyd 6y ago100 MB / app is significant, especially on laptops. Slack used to use so much memory on Linux that I couldn't afford to run the desktop app and ran it inside a Firefox tab for years... seems to have gotten better somehow.