Rusty V8 is now stable! With zero-overhead bindings to V8 APIs, memory safety through Rust’s ownership model, and great docs, it’s battle-hardened and production-ready. From here on, Rusty V8 will follow Chrome versions for predictable upgrades. deno.com/blog/rusty-v8-…

A couple of months ago, me and Surma did an OTMT episode on "Are web components worth it?", it wound up both framework and web component fundamentalists, so maybe there's something in it 😀 offthemainthread.tech/episode/are-we…

🔊 We're finally getting a fully stylable <select> element! Me and Surma dive into the details, including 10 web platform features we got along the way. ⬇️ Listen here ⬇️ offthemainthread.tech/episode/stylab…

I'm still not quite sure which decisions I made in life led to me doing something I never thought I'd do: starring in a commercial

ICYMI: In the latest episode of OTMT Jake Archibald told me all about the new, completely stylable <select> element, and the 10 underlying web platform features that were spec'd to make this possible. offthemainthread.tech/episode/stylab…

I love what keybr.com thinks Rust code looks like

Get your 👂ears ready for a brand new OTMT episode! A while ago we talked about Bazel, and now it's time to take a closer look at Nix! How does it work? Is it any good for web development? In this episode, Jake Archibald and I try to provide answers. offthemainthread.tech/episode/nix/

🔊 ICYMI: Surma talked through Nix in the last OTMT, comparing it to other build systems we'd looked at in previous episodes offthemainthread.tech/episode/nix/

🎧 A brand-new OTMT episode should be in your podcast players by now: The TC39 Roundup 🌶️ Drama Edition — Part I I talk to Jake Archibald about the TC39 Structs proposal and how it is a big step towards shared-data multithreading in JS. offthemainthread.tech/episode/tc39-s…

I apologize for splitting the last OTMT episode into two parts. It was sincerely unplanned. 🎧 Part II of the TC39 Drama 🌶️ Roundup is now out! In this one, I talk to Jake Archibald about JS0, which proposes to split JavaScript into two specifications. offthemainthread.tech/episode/tc39-j…

Dominic asked me to look at learn-wasm.dev ahead of time and I think it’s an excellent (and interactive!) learning resource! More importantly, tho: Dominic Elm wanted to hear all my feedback, which means he really cares about teaching the subject, not just getting paid.

Ooh just caught this #OTMT episode on customizable select 😎 Always love to hear Surma and Jake Archibald chat about the web (and especially the features I’ve been working on for the past few years) 🥰 offthemainthread.tech/episode/stylab…

🔊 It's new OTMT time! Me and Surma chat through some newer View Transitions features that have recently landed in browsers, and some things that might land this year. ⬇️ Pop this in your ears ⬇️ offthemainthread.tech/episode/new-vi…

Wait, am I dumb? What does NodeJS' WASI implementation only accept file descriptor numbers for stdio? Why don't they allow a Readables/Writables? How are you supposed to capture the output of a WASI module? nodejs.org/api/wasi.html#…

Folks who know their way around the TypeScript type checker, I need help: gist.github.com/surma/be14ca81… How do I figure out what types the type parameters have been bound to given a `CallExpression`? I know the answer is in `resolvedSignature.mapper`, but that’s not a public API.

Unexpected dangers of vibe coding: Somehow git ended up tracking its own .git folder and now I can't commit anymore :3

CSS uses a complex algorithm to decide how to animate transforms. If you get it wrong, as many folks do, you end up with an unnatural animation. Here's how it works, and how to avoid the pitfalls. jakearchibald.com/2025/animating…

Convince me I am wrong: This should not be a type error, right? - I asserted it’s an object - I am using `?.` for property access typescriptlang.org/play/?#code/GY…