I guess that sounds like the normal web/progressive web apps/web archives (especially with the push to more platform APIs in browsers)? Also, Tauri uses the system's WebView2/Webkit runtime, so it essentially works like this already.
It seems to be wrapping drizzle, with astrodb just being a way to deeper integrate it into the framework and adding some ease of use features. Also seems like a nice way to support the development of astro by using their hosting service.
As far as I can see from looking at their repo, Drizzle isn't a wrapper for Kysely though? You can use Kysely or other query builders with drizzle, but it has its own query builder too.
Yeah, the only unsafe code right now is using this trait to prevent some duplicate bounds checking when reading/writing to memories that wasn't being optimized by the rust compiler. Shouldn't be too much of a performance difference for code that's not too heavy on memory access, made about a 5-10% difference for the selfhosted benchmark if I remember correctly though.
WASI is one of the next things I want to explore. Right now, there sadly doesn't seem to be any self-contained implementations for the recently released WASI preview 2 out there, and TinyWasm also doesn't have support for the WebAssembly Component Model yet.
For performance, I have some very preliminary benchmarks, but this is something I want to go into more as part of my upcoming bachelor's thesis.
From the documentation, it seems like there is 0 mercurial support. It's its own separate version control system that diverged years ago. You can either use the sapling scm client or git.
