Episode 108

TanStack DB: Reactive Apps Without Firebase

On deck today: 🔥 Cloudflare & Perplexity’s data scraping dispute, 🚀 Vercel supercharges its AI SDK in v5, ⚡ and TanStack DB gives you live, reactive data without Firebase. 🎧 Developer drama & game-changing tools await.

Full Description

There’s drama brewing between AI-answer engine company Perplexity and hosting platform Cloudflare, which recently declared it would actively block AI bots from crawling websites without the owners’ permission. Cloudflare received complaints, set up its own test sites, and then asked Perplexity pointed questions only those sites could answer - and got answers! Perplexity claims it only gets data for the answers and doesn’t use it to train its models, but who really knows whether that’s true or not. A new murky grey area around scraping site data for different AI purposes has just sprung up. Just two years after Vercel launched v1 of its AI SDK, it has dropped v5, and it’s got some major improvements. It’s rebuilt the `useChat` hook from the ground up, improved tool calling and added dynamic tool handling, added more agentic loop controls, Zod 4 support, a global LLM provider, and it works with React, Svelte, Vue, and Angular. That’s just the tip of the iceberg, but it seems like Vercel’s got a winner on its hands. Never one to rest on its laurels, the team behind the TanStack universe unveils TanStack DB. TanStack DB extends TanStack Query with collections, live queries and optimistic mutations client side for building super fast apps on sync without needing to lock in to Firebase. In Lightning News this week, OpenAI released GTP-5. It’s better at all the things: writing, coding, and health questions, but are the improvements going to be so great we’ll actually notice? Time will tell. Also, in disappointing news, Cognition, the AI company that scooped up the remains of Windsurf, has laid off the Windsurf employees it acquired, or told those who remain to expect 80-hour, six day a week, work weeks: another way of effectively reducing headcount. Let’s hope this doesn’t set a new precedent in Silicon Valley.