Maybe the situation only sucks on OS X. On Linux you could hopefully swap it out with a new one on build, and it isn't based on WebKit which is slow to support lots of stuff. Either way, I think perhaps Tauri should provide a way to optionally use its own build of the rendering engine and a preset/example configuration that uses the included one for the platforms that are up to date and its own build of a rendering engine for OS X and possibly Linux.

Well, there we have the whole issue that Web has literally become ChromeOS for all practical purposes of who is driving it, and browser market share.

It is called Webview2, because the first MSHTML.dll replacement was based on the original updated Edge engine, which Microsoft dropped for their own Chrome fork.

So either one cares to use portable Web development practices, or whatever Chrome does, with the side effect to increase its market share even further.