In the back half of my batch, job search and life have begun to cut into my RC time just a little. I’m feeling a little bit less productive as a result, but did get some stuff done:
-
The
wasmtime-dlblog post is out, which is my longest post yet (both in terms of my RC batch and all the posts before it). I’m pretty proud of it and feel excited to write more deeply here. -
To get that blog post looking good, I wrote and used an NPM package to generate HTML for Obsidian callouts.
-
I did a couple playtests of concerto, an audiovisual webtoy I worked on in the first half of my batch. It’s pretty much ready for me to write it up and share.
-
My implementation of browser.engineering is up to the start of chapter 4. I can parse a subset of HTML, but not do anything with it yet.
-
I made two changes to how Brick’s runtime works:
- Instead of requiring it to be built manually, I set up a Rust build script so that the runtime will be automatically rebuilt.
- I wrote a small crate to expose some things that were previously internals in the Rust compiler’s output.
With these two changes, I can now link the runtime module directly to the compiled binary with wasmtime’s Linker interface. Previously I had been writing the wasmtime bindings by hand; this is a big ergonomics improvement. It also tees up the improvement I’m trying to make in week 8, which is linking the application and runtime within the compiler itself.