This is what frustrates me with JS development/the ecosystem - why use Astrodon instead of Tauri directly, with deno and whatever else you want? Sure maybe a bit quicker to get started, but there's more unknown/unfamiliar, another set of docs to look at, another thing that could be the cause when something goes wrong, just unnecessary indirection.<p>Or put another way, why isn't this just a template repo, why does it need it's own 'community', versioning, plugin system etc., it just seems like an annoying level to have a framework at to me - on top of Tauri but beneath any svelte/vue/etc. framework you might use.
Hopefully we'll get cross-platform (desktops, mobile, and web) GUI libraries that aren't using webtech on non-web platforms soon. Flutter is already viable, I believe. There are also some interesting movements in Rust-land: Lapce uses Druid to run on all desktop platforms. Sadly, neither Druid nor Iced support the mobile OSes yet. But eventually we might be able to forget about all these Electron and Electron-esque messes.
Lovely to see this space continue to grow.<p>Despite the hate it gets, Electron is an incredible tool to be able to quickly create a decent native experience (and as someone who uses linux - I tend to get native apps with company support, which is <i>miles</i> ahead of where I was 10 years ago).<p>I'm glad to see folks playing around with the native installed webviews - now that MS is all in on webview2, this feels like a good solution to some of the bloat required by locking a chromium version in electron.<p>Slightly more likely to hit compatibility issues across machines, but for most apps not using cutting edge apis - not too much of a concern.