Co-author of https://wasmgroundup.com — learn Wasm by building a simple compiler in JavaScript.
Prev: CDG/HARC, Google, BumpTop
I just took that and wrote some scripts to do some additional processing on it (resolving short links, etc.)
I just took that and wrote some scripts to do some additional processing on it (resolving short links, etc.)
If I had remembered, I would have probably just used that :-)
If I had remembered, I would have probably just used that :-)
I extended it to be able to able to parse the download and render the downloaded archive (with lots of help from Claude Code).
I extended it to be able to able to parse the download and render the downloaded archive (with lots of help from Claude Code).
Whereas in UI, there's a lot more top-down information flow (props).
Whereas in UI, there's a lot more top-down information flow (props).
For @ohmjs.org, I’m looking at how to support fully incremental pipelines (eg parsing → codegen, all incremental). I know about Salsa (github.com/salsa-rs/salsa); what else should I be looking at?
Whereas with tagged unions, you more often have a switch on `obj.kind` and then monomorphism within the individual cases, no?
And I wonder if the `obj.kind` access would go through a shared transitional map, and thus be fast? But not sure.
Whereas with tagged unions, you more often have a switch on `obj.kind` and then monomorphism within the individual cases, no?
And I wonder if the `obj.kind` access would go through a shared transitional map, and thus be fast? But not sure.