https://kolistat.com/blog/ 2026-06-10T00:00:00.000Z Notes from the founder on building modern tooling for clinical and tabular data — SAS, DuckDB, WebAssembly, and the craft of byte-parity engineering. Massimo Meneghello https://kolistat.com/blog/welcome/ 2026-06-10T00:00:00.000Z 2026-06-10T00:00:00.000Z Massimo Meneghello

Notes from the founder on building modern tooling for clinical and tabular data — what we ship, how we build it, and the trade-offs that show up along the way.

<p>KoliStat is the umbrella over three products that answer the same question: what would clinical and tabular data tooling look like if it were built today, with the web as the runtime and DuckDB performance underneath? <strong>KoliLang</strong> is the browser-native SAS interpreter — closed-source, compiled to WebAssembly, and built to match SAS to four decimal places (coming soon). <strong>Bedevere</strong> is the tabular data visualizer and DuckDB SQL editor. <strong>the-stats-duck</strong> is the open-source DuckDB extension that supplies the statistics.</p> <p>This blog is for the engineering notes that don't fit on a product page: pieces of the SAS dialect we had to model from scratch, DuckDB extension internals, WASM ABI design decisions, the macro evaluator, the PROC FREQ output spec, and why a particular byte-parity bug took two weeks to find.</p> <p>Cadence will be irregular. The work itself drives the topics: when something interesting lands in <a href="/products/kolilang">KoliLang</a>, <a href="/products/bedevere">Bedevere</a>, or <a href="/products/the-stats-duck">the-stats-duck</a>, it gets a post. Subscribe via the <a href="/feed.xml">Atom feed</a> or just check back — no newsletter, no comment section. That part is by design.</p>