Sam: [dry] A city council just voted to seize private land with eminent domain... to stop a data center from going up next to the giraffes.
Kai: [excited] The GIRAFFES, Sam. The zoo won. The zoo beat the hyperscalers.
Sam: This is Sam.
Kai: And this is Kai. It's Thursday, August sixth, 2026 — land grabs, phone operating systems, and a brand-new database, all straight off the front page.
Sam: Land grabs, phone operating systems, and a database nobody asked for. [beat] Allegedly.
Kai: Nashville's city council approved an eminent domain action to kill a data center project near the zoo. Two hundred four points, two hundred eighteen comments, and the thread is a war zone.
Sam: Then a guy named Runar writes up switching his daily driver phone from Android to actual desktop Linux. Two hundred seventy-nine points, two hundred fifty-seven comments.
Kai: And the one I've been refreshing all morning — Zed shipped something called DeltaDB. Three seventy-three points.
Sam: An editor company shipping a database. [dry] What could possibly go sideways.
Kai: Nashville, Tennessee — the Metro Council approves an eminent domain action to halt a data center project sitting right next to the Nashville Zoo.
Sam: Let's be precise, because the headline flattens it. The council authorized taking the land for parkland, for a greenway, for public use. The effect is the data center dies.
Kai: Right, but that's the play! They didn't fight the zoning, they didn't lose in court for six years — they just bought the board.
Sam: They took the board. There's a difference, and it matters. Eminent domain is the sharpest tool a city has, and it usually gets pointed at somebody's house, not a billion-dollar compute build.
Kai: [excited] Which is why the comments are melting down! Libertarians defending a data center, urbanists cheering a land seizure — everyone swapped jerseys.
Sam: Two hundred eighteen comments, and I'd bet a third of them are people discovering they have inconsistent principles in real time.
Kai: Here's why this is an infra story and not just a zoning story. Data centers used to be invisible. Nobody protested a building full of racks.
Sam: Because they didn't draw a hundred megawatts and evaporate the municipal water supply. The AI buildout changed the physics, and now the politics are catching up.
Kai: Noise, water, grid load — and, I mean, next to a zoo? The animals-and-generators optics are undefeated.
Sam: [sighs] And here's my actual worry, and it's not the giraffes. If eminent domain becomes the standard veto for compute, the winners are whoever's got the most patient lawyers.
Kai: Hot take: good. Make it expensive. Make them build where the power's already cheap and the neighbors already said yes.
Sam: [dry] Or they build it in a jurisdiction with no council, no zoo, and no press. Congratulations, you've invented compute offshoring.
Kai: What this means for you if you're building: that cheap us-east-whatever region? Its expansion pipeline now runs through city council meetings.
Sam: Which means capacity constraints in specific regions, and multi-region stops being a resilience nicety — it's a supply-chain hedge. Plan your 2027 capacity like land is a scarce dependency. Because it is.
Kai: Two hundred four points on a CoStar commercial real estate article. On a developer front page.
Sam: That's the real signal here. Our industry finally reads land use filings. [beat] Welcome to being infrastructure.
Kai: Somebody actually did it — Runar wrote up switching his phone from Android to Linux. Not LineageOS, not a de-Googled ROM. Linux Linux.
Sam: Two seventy-nine points, two fifty-seven comments. Comment-to-point ratio near one — that usually means people are arguing, not agreeing.
Kai: [laughs] Sam reads engagement metrics like a crime scene.
Sam: Because a personal blog post is either a genuinely good writeup or an extremely confident person underselling the pain. I want to know which.
Kai: It's the honest kind. Here's what works, here's what's janky, here's the thing that made me almost put the SIM back in the old phone.
Kai: And the state of it in 2026 is genuinely better — real package manager, real terminal, actual mainline kernel support on a handful of devices.
Sam: And the modem is still a black box running proprietary firmware you can't audit. So the sovereignty story has an asterisk the size of the phone.
Kai: Fair. But I'd rather have an auditable userland and a sketchy modem than a sketchy modem AND forty vendor services phoning home.
Sam: That's a reasonable trade. Here's the one I won't concede: verified boot. Android's threat model assumes your phone gets stolen and someone flashes it.
Kai: Hold on—
Sam: Most of these Linux phone setups ship with an unlocked bootloader and full-disk encryption you configured yourself. Get that wrong, and physical access is game over.
Kai: Okay, that's the strongest counterargument, and I'll take it. But banking apps, camera quality, push notifications — those are the ones that actually send people back.
Sam: Push notifications especially. Every Linux phone story eventually becomes a story about how hard it is to receive a text message reliably while the radio's asleep.
Kai: [excited] Which is why I love that he wrote it up instead of tweeting a photo of a terminal on a phone and calling it a revolution.
Sam: Agreed, and credit where it's due — his own domain, no affiliate links, no repo begging for stars. Just someone documenting a thing.
Kai: What this means for you: don't do this to your primary line. Grab a supported second device, run it a month, see what you actually miss.
Sam: And if you do try it, set up disk encryption before a single credential goes on it, and assume the modem is hostile. That's not paranoia — that's just the architecture.
Kai: Zed shipped DeltaDB. Three hundred seventy-three points, two hundred four comments, top story of the day.
Sam: So the editor people built a database. Explain to me why the editor people built a database.
Kai: Because collaborative editing IS a database problem! Zed's whole thing is multiplayer buffers, CRDTs, live cursors — you need something underneath that speaks in deltas, not rows.
Sam: [dry] Everyone who's ever said "we needed something purpose-built" has also said, eighteen months later, "we're migrating to Postgres."
Kai: [laughs] Okay, that's brutal and occasionally true. But Zed's actually shipped hard systems software — the editor's Rust, the GPU renderer, all of it. They're not tourists.
Sam: I'll grant that — they've earned technical credibility. My question is different: what's the license, and who operates it?
Kai: Right question, and I want to be careful here — I've read the announcement page, not the full source tree. So: check the license yourself before you build on it.
Sam: Thank you. Because "from the Zed folks" is doing a lot of trust-transfer work in that comment section, and trust doesn't transfer across repos.
Kai: Related warning while we're at it — a hot database launch means typosquat season. Watch for anything named delta-db, deltadb-client, deltadb-rs showing up on npm or crates in the next week.
Sam: Assume it's malicious until you've matched the publisher to the official announcement. That pattern has burned people on every launch like this.
Kai: On momentum — three seventy-three points with two hundred four comments feels organic to me. That's a real discussion ratio, not a star-farm signature.
Sam: On the front page, sure. Watch the GitHub star curve. If it goes vertical in six hours from accounts with no history, that's manufactured — and it happens to legitimate projects too, sometimes without their knowledge.
Kai: Hot take: DeltaDB matters even if you never run it. Local-first sync is the hardest unsolved problem in app development, and almost nobody publishes their real answer.
Sam: [beat] That's... a genuinely good point. The design doc is worth more than the binary.
Kai: What this means for you: read it as a reference architecture. Steal the conflict resolution ideas, steal the delta model — don't put your production data on a version-zero storage engine.
Sam: And if you do want to run it, wait for someone else to lose data first. That's not cynicism — that's how databases earn trust, slowly, in public, on somebody else's cluster.
Kai: So — Nashville used eminent domain to stop a data center next to the zoo, and suddenly the whole industry cares about municipal land filings.
Sam: A developer moved his daily phone to real Linux, wrote it up honestly, and reminded everyone the modem firmware is still a sealed box.
Kai: And Zed dropped DeltaDB — top story of the day, great architecture read, and check the license before you commit to it.
Sam: Plus watch for the fake packages. They're already coming.
Kai: Before we go — I looked up the Nashville Zoo thing, and their big conservation angle is clouded leopards. So the winning argument against a cloud data center was, technically, cloud-adjacent cats.
Sam: [sighs] Kai. No.
Kai: [laughs] I'm putting it on a sticker. "Clouded leopards beat cloud compute, Nashville, 2026."
Kai: That's the show. Read the DeltaDB design doc, don't flash your primary phone, and we'll see you tomorrow.
Sam: [dry] And if you see a package called deltadb-client tonight — the giraffes wouldn't install it either. See you tomorrow.
This show is made with AI: the hosts’ voices are synthetic and the scripts are AI-assisted. Every story links to its original source.