The Boscop one is just bindings for https://github.com/zserge/webview which is only MSHTML on Windows not Edge. The tether one appears Rust only which means I have to expose my own C FFI layer to use in other langs. I want them to combine and give me the best of both! :-)
Hey! Original Webview author here. I am aware of the issue of MSHTML vs Edge, and I would really love to support Edge. With the new cppwinrt included into Windows SDK it should be possible - it's just plain C++17 (and then we need a small C wrapper to make it compatible with Cgo). But so far I'm failing miserably to even build a minimal WPF app using cppwinrt. Still, the hope remains, and any help is highly appreciated.
Or maybe we should build a separate DLL for Edge and call it from the webview library? Not sure how that will work with the UWP packaging. Any expert knowledge is highly welcome and I'm open to the discussions.
I was also thinking about adding CEF bindings using dlopen, so that one could compile a binary, drop it into CEF "Release" directory and run. But I'm not sure whether it's a good idea. CEF is heavy. But it's the same on all platforms. I wonder what do people think about it?
Oh for sure. I am watching https://github.com/zserge/webview/issues/85 like a hawk and have even tried to do some self-contained binaries w/ the new WinRT libs myself with limited luck (because of the UWP packaging). I personally won't use it from Go if I can't distribute a single binary.
I have used CEF and while I love the abstraction, it comes w/ baggage. I ship CEF along w/ an app (it's the browser I'm typing this from now) and just libcef.dll is 91MB, not counting some of the tiny ancillaries. I think you are on the exact right approach and even if you want a CEF, just make sure it's not the preferred option on any platform. I have heard that MS people are working towards a usable Edge shared lib elsewhere, we'll see.
