I can't wait for Carson's talk!

Great software always took shape in conversation, not the commit. With agents, the conversation that generates the code is becoming the true source of our software. And Git can't keep up. So we built something that can. Meet DeltaDB: zed.dev/blog/introducing-del…

Me in 2019: "npm has a huge vulnerability, everyone should disable install scripts, npm should make that the default, I predict a big worm by 2025" npm in 2025: (has first big worm of several) npm in 2026: "we're disabling install scripts by default" 🎉 youtube.com/watch?v=okrB3aJt…

I did @CompileExplore's monthly accounts, and for the first time in ages we only broke even. Usually we run at a small surplus & we have a year contingency saved up. If you want to support us: * Buy stuff: shop.compiler-explorer.com/ * Patron/GH: "Other" menu on CE Please repost. thx

1996 hypers not known for shipping high-quality software: "In the near future, everyone will be programming this way; get on board the OOP design patterns and UML diagram train now so you don't get left behind" 2026: ahhh I'm kidding we don't have any equivalent of that today

This speaker lineup is off the hook. I'm so excited!!!

Email subject line: "ACTION REQUIRED:" Narrator: "It was not."

We're working to improve the Mermaid diagram experience in Zed. This week's stable will feature faster and more accurate rendering. More improvements are coming.

I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem. As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)! I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work. It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results? 88ms => 1.5ms 150K allocs => ~500 allocs Incredible right? Nope. My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path. This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput. The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity. Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.

The next Zig Day Seattle (WA) is going to be on Jun 13! Make sure to RSVP if you plan to attend! zig.day/usa/seattle/2/

I get so much joy out of @songkick's email subject lines, because I always read it as all of the artists performing at the same show.

I've had an overall very positive experience with GPT-5.5, but the "coder" jargon it uses...

I understand that LLMs write prose the way they do "because training set," but who are these psychopaths in the training set that put spaces around their em dashes?

Listened to the episode and it was a great one. @swyx and @rtfeldman have different perspectives on the recent AI evolution (but similar conclusions), which made it an interesting discussion!

Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10 years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored). If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update! I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it. Feeling pretty swell about this mentality with all the supply chain attacks happening.

Terminal Threads are live in Zed v1.3.5! You can now run claude, amp, pi, or any terminal-based workflow as a managed thread in the Threads Sidebar, right next to your other agent threads.

A friend is visiting Australia, and I'm specifically jealous because it's geographically possible for them to see @reliqaband live. 🤘

Systems Distributed '26 is getting closer and so is the Zig Day Boston scheduled for the day before (completely free, NO conference ticket required). Come practice your systems thinking and make software you can love with us! RSVP: luma.com/eloljzc0

My take on the bun stuff lobste.rs/s/lapqbz/bun_s_rus…