I’m glad the Bun rewrite blog post focused mostly on the methodology of the port! It’s a good post! Good work @jarredsumner.
My favorite part is the little detail about the importance of clean context agents for doing different tasks to avoid biases. I’ve found this is a good reason to not use a single long auto compacting coding session for both build and final verify.
On the cost, I think $165,000 at API pricing for Fable (didn’t verify) is an incredible deal. There’s absolutely no way an engineer with that salary would’ve been able to achieve the milestones Claude did in 11 days. No way. (Even if you break it down to N engineers paid $165K total in 11 days it doesn’t math out)
This does, however, also reconfirm my own biases which is that Fable in particular is most excellent at hard, focused tasks with clear reward functions. I’ve been tweeting about this recently.
I would absolutely use Fable for this.
The "should you read code" debate is dumb because the real decision isn't binary, it's a scale:
1. Reading every line of every diff
2. Scanning every diff, reviewing important lines
3. Ignoring diffs but understanding the 'why' of every PR
4. Spot checking PR's instead of reading every one
5. Ignoring PR's, but doing regular spot checks on the codebase
6. Ignoring the code, but spot checking agent traces to help improve the system
7. Ignoring both the code and the system, let models handle everything
Where are you on the scale?
Starting today, we are making @base_ui the default component library in shadcn/ui.
First, a bit of history. When shadcn/ui launched in 2023, it was built on Radix. At the time, nothing else came close. Headless. Accessible. Composable.
Fast forward a few years and the team who built Radix are building something new: Base UI.
lately after a big change instead of reading the diff i ask the agent for a summary of what it did in each file
anything weird sticks out immediately and 1-2 prompts later it's completely as i want it
files + functions signatures i need to know, care less about function body
FFmpeg's native AAC encoder has just been rewritten, and now beats both fdkaac and qAAC according to current metrics and listening tests.
This is not a small change. @X and @OBSProject use it, as well as many others. It's been a critical piece of the internet, and is now the best
Everyone said this was impossible.
ClickHouse is a massive multi-threaded engine. Porting it to WebAssembly — a single-threaded runtime — was supposed to be a non-starter. Every AI we asked told us the same thing: can't be done.
But years of working on this engine gave me a different intuition. From first principles, there was no fundamental barrier. Just a hard problem that everyone had assumed away.
So we pointed AI at it — refactor, regress, repeat — instead of taking "impossible" for an answer.
The result: https://t.co/OgmJ09qJpC
A full ClickHouse OLAP engine, running entirely in your browser tab. No server. Query local files and S3 Parquet in-process.
Huge thanks to @wudidapaopao for the relentless work that made it real.
My entire AI stack is now Chinese 🇨🇳
87% cheaper. same revenue
swaps by task:
1. reasoning / backend brain
Opus 4.8 → Kimi K2.7
benchmark gap: ~8% · price: ~11x cheaper
2. code generation
GPT-5.5 → Qwen 3.7 Max
benchmark gap: ~18% · price: ~7x cheaper
3. agent loops + tool calling
Sonnet 4.7 → GLM 5.2
benchmark gap: ~3% · price: ~5x cheaper on input
4. cheap volume / bulk processing
GPT-5.5 mini → MiMo V2.5
benchmark gap: ~6% · price: ~12x cheaper
5. image generation
GPT-Image-2 → Wan 2.5
benchmark gap: ~5% · price: ~8x cheaper
6. video generation
Sora 2 → Kling 3.0
benchmark gap: roughly equal · price: ~6x cheaper
[ result after 30 days: ]
operating costs dropped 87%, output quality dropped 4% on average, revenue unchanged
the most important that these models will be not banned in a month and i can run them locally
nobody will steal my data and i can learn them as i need
full article drops tomorrow with:
> exact routing logic per task type
> the 2 cases where I still pay for American
> the migration playbook anyone can copy in a weekend
VERY IMPORTANT to get migrated now, while it's not too late
Two months ago I was fired by Google for creating the Google Workspace CLI. It went viral, hit #1 on Hacker News, gained thousands of GitHub stars and many thousands of actual users in just a couple days.
It was an incredible, confusing journey, from directors and leaders asking what they could learn from the tool to getting grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories.
I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted. But the fear wasn't specific to my CLI, it was a broader fear in what agents meant for Workspace. Either way, the irony of my termination was the announcement at Google Cloud Next two days before I was fired that an official Workspace CLI was coming.
I want this out there because it is easier for me to explain my story and it is an experience I want to fully own. It's also part of my healing.
Nearly 7 years at Google was an incredible opportunity for me and I was fortunate to have wonderful teammates and a manager that fully supported me through these last few months. Thank you.
Anthropic 2026 Hiring Announcements:
May 19th: Andrej Karpathy
June 19th: John Jumper
July 19th: Alec Radford
August 19th: Jeff Dean
September 19th: Alan Turing (resurrected by Fable 5)
The backward compatibility guarantees that @nodejs is asked to provide are incredible. They are often asked by companies that do not contribute anything back.
I'm sorry when we break things unexpectedly, but asking to support a package that was last updated 3 years ago is really tough.
📣 TypeScript 7's Release Candidate is now out! 📣
The new native port is almost here. Try it out on your codebases, and make sure your team is ready for the upcoming 7.0 release!
https://t.co/WBCvxYHoJX
I had a lot of Fable tokens to use up before my weekly reset, so I made this live 3D map of London with Three.js
Every train, bus, boat and plane is real and live right now!
- Tube, bus and riverboat data from TfL
- National Rail trains from Darwin live departure boards
- ADS-B for planes and helicopters
- AIS feed for boats and ships
- Map data from Overture and OpenStreetMap
Trains and buses have no GPS feed, so their positions are inferred from arrival countdowns and departure boards, then animated along the track/route geometry
VoidZero is joining Cloudflare.
Our mission stays the same: to make JavaScript developers more productive than ever before. Vite, Vitest, Rolldown, Oxc, and Vite+ remain MIT-licensed. Evan and the VoidZero team will continue leading them.
Cloudflare shares our commitment to open source. Together, we can keep investing in the tooling developers rely on every day, while bringing the Vite ecosystem and Cloudflare’s platform even closer together.