The new Edge browser uses Chromium, not WebKit, so still two different browser engines to deal with (essentially Chrome vs Safari).
99.9% of the time your pages render the same on Safari as they do in Chrome because it's effectively WebKit.
The only real difference between WebKit based browsers is experimental features. They all follow the core standards now which IE11 didn't.
When I tinkered with https://github.com/webview/webview on macOS a minimal Hello World application was around 26 kBytes (kilo, not mega), which is about 7000x smaller than a default macOS Electron instance (173 MBytes).
so I wouldn't have to worry about various electron app packages shipping with versions of Chromium from three years ago?
But at least you can call out into native code and native operating system APIs, unlike "real" web applications.
So your binaries can be really small too. Seems like faster start up times also.
It uses native webview so no electron. Let's you effortlessly bind JS functions to those in Go.
V2 is in the works and will effectively bring the best features of electron window management (menus, frameless windows, drag regions etc) over to native webview.
Currently uses IE11 on Win 10 but V2 will only support Edge so you get WebKit across the board.