webassembly-language-runtimes VS go-sqlite3

> so I wonder if there's something holding back Python + WASM

Yes. The problem is that may python libraries involve compilation of c, rust or other native languages that themselves need a WASM toolchain configured to cross compile to WASM correctly, and potentially patches to support the platform.

This toolchain support is coming though. See pyodide.org for one example.

But if you just want to grab python.wasm from somewhere and run it on the cli, take a look at something like https://github.com/vmware-labs/webassembly-language-runtimes...

WMWare labs [1] managed to compile Python/Ruby/PHP into WASM distribution. This works if you want to run the language interpreter but is limited when you want your WASM runtime (host) to run in parallel of your own program. This leads to the creation of the "reactor" concept by the community [2].

In the python WASI reactor, we load the libpython compiled for WASM and add a Rust reactor layer. Currently, it supports dynamic registration of Python lambdas and we are working on adding support for whole functions/packages.

[1] https://github.com/vmware-labs/webassembly-language-runtimes

The Python builds from the WebAssembly language runtimes [0] project target the WebAssembly System Interfaces (WASI) [1]. It allows the Python interpreter to interact with resources like the filesystem.

Many server-side Wasm runtimes supports WASI out of the box. For the browser, you need to provide a polyfill to emulate these resources like the one provided by the WASI team [2].

Regarding SQLite, these builds include libsqlite so you should be able to use it :)

- [0] https://github.com/vmware-labs/webassembly-language-runtimes

- [1] https://wasi.dev/

- [2] https://wasi.dev/polyfill/

Hello salaboy

Of course getting and gems etc gets weird in wasm..

Anyway, thanks to VMware labs for publishing interpreter wasm builds, people can play around. https://github.com/vmware-labs/webassembly-language-runtimes...

Random, but enjoy.

Hey! A WasmLabs team member here :). We're planning to port several runtimes as part of our WebAssembly Language Server initiative [1]. Porting things to Wasm+WASI is sometimes challenging. There are some deep-dives in our blog around this topic [2].

[1] https://github.com/vmware-labs/webassembly-language-runtimes...

[2] https://wasmlabs.dev/articles/php-wasm32-wasi-port/

Yep, I just made it tweakable at build, which was always the intent, although I expect the default to be popular.

https://github.com/ncruces/go-sqlite3/blob/67d859a5/vfs/adia...

That's unfortunate about the default parameters, but note that you can also replace the KDF altogether (besides just not using it).

You just need to implement this interface, with any HBSH construction and KDF:

https://github.com/ncruces/go-sqlite3/blob/67d859a5/vfs/adia...

If you keep the HBSH and change the KDF, your file format will be “compatible.”

struggling figuring out how to make my cgo sqlite cross-compile to Windows

Plenty of people trying to fix that.

There's at least:

https://modernc.org/sqlite

Then there's https://github.com/zombiezen/go-sqlite that actually builds https://crawshaw.io/sqlite on top of modernc.

And there's mine that has both a low level and a database/sql driver builds and runs everywhere Go does: https://github.com/ncruces/go-sqlite3

If you're interested both SQLite's and my memdb VFSes implement safe locking.

Depending on your familiarity with Go, mine maybe easier to follow, or not.

https://github.com/ncruces/go-sqlite3/blob/f1b00a9944730eaa9...

One thing I tried to make sure, to avoid the pitfall modernc is having, is to make sure building "the WASM BLOB" is easily reproducible with widely available tools:

https://github.com/ncruces/go-sqlite3/blob/main/.github/work...

I do apply some light patches to SQLite, but so far they've always cleanly applied, and I can produce a new release within hours of being notified of SQLite releases.

Disclosure: I'm working on alternative Cgo-less bindings for SQLite, using wazero.

https://github.com/ncruces/go-sqlite3

One of the problems of the modernc approach (IMO) is that they're not just transpiring CPU/compute stuff, but entirely OS/platform stuff.

Each Go file of theirs is a xxx_os_arch.go that starts with 100s of OS-#defines-as-consts, and goes on to transpile fully #ifdefed code.

It also implements antithetical (in Go) stuff like goroutine local storage, because libc pthreads can't live without it.

And all IO is via direct syscalls that will never play nice with the Go scheduler, because, again this is OS level stuff.

WASM defines a cross platform CPU and an ABI, and using that for compute and the bottom OS layer in Go you get (IMO) a nicer end result.

Given the hard task of generating decent code from WASM at load time (wazero's compiler is pretty naive, a better one is being developed, but it will take seconds to generate good code for anything non trivial like SQLite) I wouldn't mind having a solution that translated to Go, or Go ASM, at build time.

The github.com/ncruces/go-sqlite3 is a link.

Using the stack pointer global is an interesting hack. I'd never thought of that. Need to compare with what I'm doing for SQLite (a kind of per connection arena).