2 ms·
Sounds you only need to create the APIs for calling into WASM if so, so as long as your language of choice can do that, you're good to go.
by embedding-shape 11mo ago
Sounds you only need to create the APIs for calling into WASM if so, so as long as your language of choice can do that, you're good to go.
- dboreham 11mo agoThat adds extra unnecessary complexity. The code is written in C. There are C compilers for all CPUs. So just call the C code from <other language that's not JS>.
- hombre_fatal 11mo agoWell, a project has scope. Looking at the repo, it started as postgres-in-the-browser. An abstract interface with C and wasm as targets is just more scope. But it looks like the hard part of patching postgres to librar-ify it is already done agnostically in C. So you just need to ctrl-f for "#if defined(__EMSCRIPTEN__)" to impl those else branches and port the emmake file to make.