1. Piping from stdin vs. in memory is not a fair comparison 2. Comparing CLI perf on a single file where the overhead is mostly just Node startup time 3. No feature parity at all I’d suggest you run it on a large production codebase that currently uses prettier and compare the perf and diffs
Catch the full Community Showcase: www.youtube.com/live/xzoF8q0... Jeremy Olson’s AI agent, Max, went out on the internet, bought a domain, and chose his own stack. Including Netlify. No prompt. No steering. That’s…new.
Missed our latest Community Livestream? The replay is up.
Catch the community roundup, builder highlights, and the surprise roster of guests here: 👇
www.youtube.com/live/xzoF8q0... 
fwiw, not dramatically wrong, but the main problem is that passing the bound method directly to the listener means that abort is called with the event as an argument, which is treated as the 'reason' developer.mozilla.org/en-US/docs/W... so it changed behavior 
snowy run to the library to drop off and pick up some books
jarred wrote about how claude identified and fixed a memory leak in anthropic's sdk (the sdk generator code is from stainless, a separate company) claude's fix was wrong
Whoops, forgot the links:
chriscoyier.net/2023/10/11/r...
remysharp.com/2023/09/26/n... Found it! Looks like originally from @remysharp.com's "404 No More." Looks like you answered Chris's wish:
> Still, I could see this implemented at different levels. Maybe the speed is a solveable problem. Like a browser extension? A WordPress plugin? I remember reading about dead link fallbacks on @chriscoyier.net's blog a couple years ago which I thought was a nifty trick 
oh man, adam neely's film-length critique of suno is spectacular: www.youtube.com/watch?v=U8dc... 
fixed it! we shipped a fix that makes the 'screen of death' no longer appear!
You might wonder: What is a panic though? A panic is basically Rust's way of saying "something unexpected happened and I can't safely continue." Or to put it in JS terms: It's like an uncaught TypeError or RangeError crashing your Node process, except it happens at the native/system level.
Rolldown can panic sometimes... but we make sure you never have to!
It's rare, but when it happens, you won't be staring at a cryptic stack trace. @rolldown.rs straight up tells you it is not your code. And a link to report it so we can fix it fast.
Good error messages => good DX 
Claude Code with Netlify Agent Runners now runs on Opus 4.6 via AI Gateway.
Improved performance over 4.5, same workflow, no action required.
www.netlify.com/changelog/cl... basically on zero days this year has any news about new llm models or whatever seemed more important than the absolute cultural and moral rot of this country
today's "searching for mapbox and observablehq on twitter results": a groyper used mapbox to make a racist map and mapbox shut them off, so a bunch of assholes are crying a pedocon is using an observablehq map of historical age of consent to downplay the epstein files 2026 is 2026 in every corner
A new community program is landing Monday. Helpers, you’re gonna like this 👀
working on it! :)
great to be a programmer at google, terrible to be a programmer using google. (sorry 🌶️ but this makes ex-google people marginally more annoying than other ex-faang people)
they bundle every sdk with types for every google service (around 320 of them) github.com/googleapis/g... perusing the @val.town npm module cache usage… 