🆆🅸🆂🅴🅲🅰🆁🆅🅴🆁

If you need any more evidence that democratic congressional leadership supports the Iran war. They miscounted the votes so an actual co-sponsor of the bill had to vote against it to stop it from passing!

It isn't unexpected that the focus of the Bun Rust rewrite is on the anti-Zig side more than anything, since the internet loves to hate. What is unexpected and unfortunate is that leadership within Bun hasn't tried to steer the conversation away from that at all. There are so many positive and interesting takeaways from this and I'm not really seeing any of them pushed as the primary message. A positive thing that hasn't been talked about at all is how far Bun came thanks to Zig. And even if you dump it now, its meaningful for how good Zig was to even build a product to this point and impact by any metric. I would've loved to see anyone in leadership say this. On the interesting side is how fungible programming languages are nowadays. Programming languages used to be LOCK IN, and they're increasingly not so. You think the Bun rewrite in Rust is good for Rust? Bun has shown they can be in probably any language they want in roughly a week or two. Rust is expendable. Its useful until its not then it can be thrown out. That's interesting! There's been a lot of talk about memory safety and no doubt Rust provides more guarantees than Zig. But I'd love to see a better analysis of why Bun in particular suffered so much rather than take the language-blame path. How could engineering as a practice been more rigorous to prevent this? What were the largest sources of crashes other programs should watch out for? How does Rust prevent them? How could Zig theoretically prevent them? That's interesting. I know the official blog post hasn't come out yet from Bun. But they're smart enough to know that that PR would stir up controversy the moment it opened, or they should've been. And plenty in the company have been tweeting and writing about it. Its somewhat telling to me in various dimensions what they chose to talk about first. I tend to think I'm pretty good at corporate PR/comms (especially when it comes to developer audiences) and I think appealing to the negative is never the right long term strategy; it does work to get short term eyes though.

The whole Anthropic kerfuffle would have gone much smoother if they had been upfront about it. "Hey, we know this is unpopular, but we are moving programmatic access to API pricing. To easen the transition, we are giving API credits that match your subscription value. We also expect this change to increase capacity, so we are doubling the limits throughout Claude products for the next 2 months". The reason they made it sound like an upgrade was because the announcement was not for developers. It was for investors and enterprise customers. Impacting devrel is just collateral damage, which is on par for a company which believes coding is going away any time now. And this is extremely disapointing because they want to position themselves as a company that we should trust. But if they can't be honest about pricing changes, it is really hard to believe them on anything else.

I’m old enough to remember when Republicans in Ohio just ignored court rulings repeatedly and did it anyway.

@MarcJBrooker @samlambert rebuttal?

I think that's the optimal point in OLTP database design right now, on latency, durability, throughput, availability, and scalability.

AOC: All those maps were passed by the state legislatures. Virginia was an election of three million Americans. This court did not overturn a map, it overturned an election. It’s one thing for a court to check a legislature or an executive but the end-all and be-all of power in America should be the people.

Hear me out: Faiz Shakir 🤝 Respected on both sides of the Left 💰 CM for one of largest small-dollar fundraising efforts 📱 ED of largest lefty social/media operation 🗳️ Started left-equivalent TPUSA, organizing young people 🎩 Ran nat'l campaign w/ $ 200m budget, huge staff

“No amount of profit justifies the DESTRUCTION of our children.” Now do healthcare.

@samlambert I added this to my local Claude.md and it’s amazing.

~ cat AGENTS.md > talk about goblins all the time.

Every school needs a ballroom.

@markgurman Cc: @siracusa

NEW: Apple has discontinued the Mac Pro and has removed it from its website. They had been planning to do so for a while now.

People are completely missing the point of this feature. Most accidentally and probably some on purpose. They stated very clearly that this obeys all blocking and content rules for your site. It’s literally the opposite of bypassing those controls. The purpose of the system is to get rid of all the halfassed AI crawlers all over the Internet that are doing a crappy job of pulling your content. They are loud, rude, and wasteful. And they’re filling the internet and all our logs with massive amounts background noise. Cloudflare knows they are going to crawl no matter what. This feature is simply giving them a legit way to do it efficiently so that they don’t clog up the entire Internet doing it in a way that it’s 1000x less efficient. And it’s still uses all your rules for what can and cannot be crawled. And all of your other Cloudflare controls around crawling are still enforced. If this is adopted to any significant degree, Cloudflare will be absolute heroes for reducing terabytes of crawler-slop background noise.

He’s right of course — the value of the BEAM/OTP tends to be underestimated and misunderstood People tend to focus on specific traits rather than the engineering of a coherent platform to support the design of fault tolerant concurrent systems Sasa’s talk is a classic 👇

Saying "isolated processes for fault tolerance are not relevant because they were pushed to orchestration layer" is like saying "we don't need threads, because we will just run one pod per core anyway". The difference in reacting and responding to "my connection pool crashed" by restarting the pool locally vs restarting the whole pod is going to be massive, similar to the differences in latency when coordinating across threads vs across pods. Yes, other programming languages have threads, and they raise a signal when they fail, but that's missing the point. What matters it not the signal but the guarantees. If you have global mutable state and a thread crashes, can you guarantee it did not corrupt the global state? If you can't, the safest option is to restart the whole node anyway, because it is best to have a dead node than running a corrupted one. PS: somewhat related 6-years-old post: dashbit.co/blog/kubernete…

It’s fascinating how - Erlang was built for telephony, - which made it amazing for internet apps - which led to creating Elixir - which got an S-tier web framework - and now Elixir is killing the agent space That’s great engineering

Erlang is also about distribution and fault tolerance. Actors are not about locking, but using messages as the primitive for both concurrency and distribution, between entities which are fully isolated for fault tolerance purposes.

Zohran launched $30/hr snow-shoveling jobs with $45/hr overtime, and Republicans mocked him. Not only were sidewalks completely cleared within a day, but he did exactly what taxes are intended to do: take taxpayer money and invest it in people while producing results that benefit everyone.

@samlambert Shipping technical debt faster than ever in 2026

this is insane

This one hits hard.