Chris Dickinson reposted
Chris Dickinson
Chris Dickinson
@neversaw.us
former Node.js TSC & NPM registry eng / systems eng (❤️ rust, bash, js, tf) / sometimes illustrator / pets cats; pronouns he/him (@isntitvacant elsewhere)
836 followers511 following116 posts
Chris Dickinson reposted
gen z (probably?) doesn’t remember having to look up the new 2002 horror film, feardotcom, by navigating to feardotcom dot com
The cultural cutoff between millennials and gen Z is that Gen z doesn’t remember 9/11. That’s kinda the defining event. But also they probably don’t remember pre Google internet. Younger gen z doesn’t remember a world where iPhones didn’t exist, either.
Chris Dickinson reposted
Chris Dickinson reposted
JSPI, the wasm JavaScript Promise Integration proposal, is now at phase 4: github.com/WebAssembly/... That means it is considered fully standardized. JSPI lets wasm call JS APIs that return a Promise. The wasm awaits it. It is still behind a flag in most browsers, but hopefully not for long!
I absolutely loved this talk. It's the endpoint of "programming as theory-building" – by turning software engineering into a rogue-like, the durable product of development is a better theory of how to solve the problem at hand. www.hytradboi.com/2025/03580e1...
I absolutely loved this talk. It's the endpoint of "programming as theory-building" – by turning software engineering into a rogue-like, the durable product of development is a better theory of how to solve the problem at hand. www.hytradboi.com/2025/03580e1...
so, ICYMI, I've been pushing along a (spec-compliant! slow!) wasm interpreter here: github.com/chrisdickins... I've gotten a lot of the structure incorrect. (quelle surprise!) Part one is to start to put cut points between "machine" and "runtime". So I'm identifying organelles of a Wasm runtime.
I had a thought last night about writing a follow-up to "understanding wasm": "building wasm" which would take a comparative look at how wasm runtimes are structured, maybe trying to link that back to VM design texts, etc
so, ICYMI, I've been pushing along a (spec-compliant! slow!) wasm interpreter here: github.com/chrisdickins... I've gotten a lot of the structure incorrect. (quelle surprise!) Part one is to start to put cut points between "machine" and "runtime". So I'm identifying organelles of a Wasm runtime.
I had a thought last night about writing a follow-up to "understanding wasm": "building wasm" which would take a comparative look at how wasm runtimes are structured, maybe trying to link that back to VM design texts, etc
But one interesting bit is the concept of a Type registry (github.com/bytecodealli..., github.com/v8/v8/blob/m...) Not all runtimes appear to support this! At a very high level it holds canonical type information for every type encountered by the engine.
Specifically, it holds type information for GC types – which can be internal, user-defined structured and arrays in addition to function types. (See wasmtime's RFC: github.com/bytecodealli...) Modules hold "collections" (via code objs) which keep individual types in the type registry alive.
so, ICYMI, I've been pushing along a (spec-compliant! slow!) wasm interpreter here: github.com/chrisdickins... I've gotten a lot of the structure incorrect. (quelle surprise!) Part one is to start to put cut points between "machine" and "runtime". So I'm identifying organelles of a Wasm runtime.
I had a thought last night about writing a follow-up to "understanding wasm": "building wasm" which would take a comparative look at how wasm runtimes are structured, maybe trying to link that back to VM design texts, etc
Chris Dickinson reposted
Replying to @hcrichardson.bsky.social
Just watched Sen King's speech on the Senate floor - thank you for that! Every American should hear this. #CourageIsContagious youtu.be/g2ptQFOi9Pg
Chris Dickinson reposted
🚀 Chicory 1.1.0 is here! 🚀 This release brings SIMD support, improved Android compatibility (API 28+), and overall performance boosts! ⚡ Read more: 🔗 chicory.dev/blog/chicory... #WebAssembly #Java #Chicory #wasm
Chris Dickinson reposted
Do you work at a company you like that is actively hiring Software Engineers? do you know someone who does? Consider referring me to them & them to me! My website homepage now has a "Hire Me!!" section with info about me, what I'm looking for, and how to contact me! esoterra.dev
This is what the dylibso team and I have been working on: a safe, portable way to install tools that Claude and other MCP clients can use. Quickly and confidently installing tools from a number of different authors and immediately putting them to use in a Claude session has been eye-opening.
It's only been a handful of days since @anthropic.com announced MCP, introducing a new standard to integrate software tools and data systems into AI applications. I see a promising future for MCP, so much that we're shipping a whole product to help see it grow!
This is enabled by Wasm! In particular, we built on top of XTP, which gave us a registry, dev tooling, and validation pipeline out of the box. It was a rocket boost. It let us build mcp.run in two weeks (& change.) Coincidentally, we would be happy for your team to try it out: www.getxtp.com
(OK, that’s my “did you know that Dylibso is a company that sells Goods and Services” bit.) Seriously neat though: we run incoming servlet code on our infra (twice!) before it hits your machine. Once in XTP to validate your servlet’s output & once in mcp.run to cache the output of the tool desc.
Matteo continues to put out clear, informational explanations about core platform architecture concepts. (I'm pretty animated by HTTP caching – designing around caching strategies was pretty fundamental to my experience at npm. You can do some pretty nifty stuff with modern CDNs these days, too!)
I’ve been talking a lot about HTTP caching recently & 2 things are clear. 1️⃣ Caching is the backbone of fast, responsive apps, but when done wrong, things get BAD 2️⃣ We are all responsible for doing caching right We've done a deep dive into HTTP caching fundamentals. https://buff.ly/3Zpg0Re