Question from someone knew very little in this domain: what stops mass adoption of WebAssembly?<p>A few years ago, I used a WASM demo website which can use a WASM version of ffmpeg to mux audio and video into a file (transcoding obviously wasn't practical, at least not at that time), and I was very impressed. I can see lots of potential of it.<p>But I still haven't see much usage of it even today.<p>(To be totally honest -- i'd rather it's <i>not</i> popular because it would make debugging websites/web applications close to impossible; but that's besides the point.)
In my job we are using duckdb compiled to wasm in our browser-based application. We store time series data in it and can query the data to show charts and logs using SQL.<p>We insert the data into the database as we collect it, then we query the database for showing charts with the query parameters (time-range, parameters to plot, etc) based on the UI controllers. We also use its built-in parquet export functionality. It works great.
Very cool -- if anyone else is curious about the WebAssembly code that powers this app, here are some pre-analyzed modules from the page:<p>337.35kB, 5 imports, 29 exports
<a href="https://modsurfer.dylibso.com/module?hash=2c72ee42bd9430029dda8c6bafc9f37143f6fe88d5f1ea950a70259ab748bcfe" rel="nofollow">https://modsurfer.dylibso.com/module?hash=2c72ee42bd9430029d...</a><p>29.77MB, 27 imports, 1215 exports (!)
<a href="https://modsurfer.dylibso.com/module?hash=2a466f0e990329d3230b869d04fc20803eae96a7feb3a3f6c93e25a77b8aed1d" rel="nofollow">https://modsurfer.dylibso.com/module?hash=2a466f0e990329d323...</a><p>18.59MB, 25 imports, 1 export
<a href="https://modsurfer.dylibso.com/module?hash=36419ed202011765222098d7701218378b67f634d50f0a4625059ae2c9860f48" rel="nofollow">https://modsurfer.dylibso.com/module?hash=36419ed20201176522...</a>
Is the site working? There seem to be broken sections: a section that just says "undefined", a large section that's blank, and a section that just says "Error: process exited with code 1.".