3 ms·

I think my silly and unserious naive response would be linear scaling bundled binaries with number of platforms doesn’t seem to be that materially different in

I think my silly and unserious naive response would be linear scaling bundled binaries with number of platforms doesn’t seem to be that materially different in terms of total size. But I see your point, didn’t consider the architectures

afiori 3mo ago
it would be sorta enough to bundle the wasm binary
- Certhas 3mo ago
  That's the idea behind the future file format: https://github.com/future-file-format/F3 https://github.com/future-file-format/F3 Bundle a wasm decoder as a fallback when native decoder isn't available.
  - mort96 3mo ago
    The issue then is that instead of just bundling a tiny 1MB sqlite library with your program, you have to bundle a huge WASM runtime. I looked at the size of wasm on my system just to get an idea and it's 46MB; that's huge. For context, I have a game I'm working on where I build stand-alone builds with all dependencies bundled. The app bundle is 14MB right now. If I added sqlite, it would grow to 15MB. If I added sqlite-but-with-wasm, it'd more than quadruple in size to 60MB.
    - mort96 3mo ago
      Ugh I can't edit now but just noticed I should've said I looked at the size of wasmtime, not "the size of wasm".