webvm VS postgres-wasm

Shameless self-promotion: https://webvm.io

Powered by a x86->Wasm JIT. Technical writeup: https://labs.leaningtech.com/blog/webvm-server-less-x86-virt...

Developer here. CheerpX for Flash runs the Pepper API version of Flash, and you're correct about the license. However, we don't do full Linux emulation just to run Flash - we emulate PPAPI and run the Flash player in an x86 JIT (CheerpX).

Yuri talks about CXFF's architecture here:

https://youtu.be/7JUs4c99-mo?t=1045

...but if you wanted full Linux system emulation, we got it! https://webvm.io

webvm has Tailscale sockets-over-WebSockets for networking: https://github.com/leaningtech/webvm

https://webvm.io/ supports WebVM runs x86 binaries in WASM on any browser w/ ("CheerpX includes an x86-to-WebAssembly JIT compiler, a virtual block-based file system, and a Linux syscall emulator") and for external sockets there's Tailscale networking.

IIUC that means an SSH client in a WebVM can connect to a (tailscale (wg)) VPN mesh

lets pre-load it into a https://github.com/leaningtech/webvm/blob/main/dockerfiles/debian_mini

Just to show how complex these can get look at this https://webvm.io/

Funnily enough, I believe that's completely achievable with enough time spent on it (probably a few weeks of an engineer working full time).

We have technology like WebVM [1] (from leaningtech / CheerP) or Copy86 [2] that already allows x86 machine code execution/emulation on the web. If you add an OCI client layer on top that is executable in the browser, it should be possible to run Docker containers in the browser.

[1] https://webvm.io/

[2] https://copy.sh/v86/

I used https://wasm.supabase.com/ to make sure some SQL commands I was writing for a blog were correct.

I miss a feature where I can share a link with some data/schema pre-seeded (maybe from a gist?)

We achieve this by mounting a compressed 9P filesystem in the VM. 9P provides a Python script which takes a filesystem folder,renames every file an 8-character name and produces a filesystem.json file representing a nested structure with files, original file names, sizes, etc.

maybe https://wasm.supabase.com tech?

Hey HN, we’re excited about this launch. This was a collaborative effort with the team at Snaplet [0].

postgres-wasm is an embeddable Linux VM with Postgres installed, which runs inside a browser. It provides some neat features: persisting state to browser, restoring from pg_dump, logical replication from a remote database, etc.

The idea was inspired by CrunchyData’s HN post about a month ago [1]. We love the possibilities of Postgres+WASM, and so Supabase & Snaplet teamed up to create an open source version. The linked blog post explains the technical difficulties we encountered, and the architecture decisions we made.

We’re still working hard on this, but it’s at a good “MVP” stage where you can run it yourself. Snaplet are working on a feature where you can drag-and-drop a snapshot into your browser to restore the state from any backup. Supabase are exploring ways we can run the entire Supabase stack inside the browser. You can find the Snaplet repo here [2], and the Supabase fork here [3]. There’s very little difference between these two, we just have a different browser UI.

Both Supabase team and the Snaplet team will be in here commenting if you want to know anything else about the technical details.

[0] Snaplet: [https://www.snaplet.dev/](https://www.snaplet.dev/)

[1] Crunchy post: [https://news.ycombinator.com/item?id=32498435](https://news....

[2] Snaplet repo: [https://github.com/snaplet/postgres-wasm](https://github.com...

[3] Supabase fork: [https://github.com/supabase-community/postgres-wasm](https:/...