Mobile chrome safari not supported , curious why

They have compiled to WASM64, the newer 64bit version of WASM. That's not available on iOS yet.

WASM till recently has had a 32bit address space, to match the limitations of JS numbers. With 64bit WASM you have to use BigInt rather than the floats that are numbers in js to address the memory.

It's only the address space that's affected - old WASM still handled 64bit math fine.

Safari is the new IE

Works on Brave (Chromium) with Android 16

I like the initiative but would love if there was a heavily stripped down version, it seems this one needs to download 95mb+. DuckDB also has a WASM version which is also not tiny but comes in at something like 36mb if I recall correctly.

What's your redline download size?

Is the point of this privacy, offline analytics, or eliminating server costs, and does that survive the download cost of 95 megabytes?

WebAssembly doesn’t run only in the browser. WebAssembly runtimes can be effective sandboxing mechanisms for embedded plugins, serverless execution, etc.

People still complain about 95mb download in 2026. It's literally 2 minutes of 1080p youtube watching.

Why bring server software to edge devices? Because its fucking awesome!

It's the equivalent of chatbots where they are reading too much into your prompt and you have to constantly tell em "don't worry about that"

if only that would work

I appreciate that in global terms I live a life of data privilege, but I really don't think a 95mb download is any problem at all if the thing I'm downloading has utility.

Aside: nice /item?id= here on this submission! 48750000.

This is impressive! What's the stack? What drives the CLI-in-browser (libghostty?) What did you compile to wasm with (rust? zig? emscripten?)

Excited on what this brings to the server-side :)