webview_deno VS deno_sdl2

I spun up the Deno Webview demo (https://github.com/webview/webview_deno) and compiled an EXE. When I run the EXE, I have two windows: the UI window and what I presume is the host process window. I only started learning Deno like yesterday but what's the state of DevTools for Deno Webview? Can I compile my Deno Webview executable with Chromium plugins like Chrome DevTools?

By the way, I was using Deno + WebView 1.2k stars, and it's working fine, but my end-users need to install the WebView runtimes... so it wasn't portable. while WebUI is totally portable.

The most updated webview bindings I know of for deno: https://github.com/webview/webview_deno

It's likely you will find some hiccups in latest deno release because it uses rust plug-ins and they are getting overhauled at the moment. Maybe a few more months before getting stabilized.

sdl2 gets around the first problem by downloading a CLI service & starting it, that speaks JSON over a TCP socket. It's a limited surface of the API, and missing some pretty basic stuff, but I could see it working ok. It's not canvas, so I'd have to translate those sort of calls to it. I discussed that a bit here and it sounds like I could blit images of the canvas to sdl2 surface, but since it doesn't support in-memory images, I'd have to implement that in sdl2, or save a "frame" image to a file, for every blit. Either way, I have the overhead of redrawing every frame as a complete image. This seems incredibly jenky, and I assume will not perform very well, but I haven't tested.