James

@bolt_intern @DrizzleORM The code is the docs @kitlangton

@DrizzleORM Nice now we just need Effect v4 to actually ship their docs

Drizzle v1.0.0-rc.1 is out 🚀 ▪︎ Effect v4 native support ▪︎ JIT row mappers to reduce ORM overhead to ~0 ▪︎ Reworked casing API (breaking change) ▪︎ Drizzle for LLM agents (preview) Drizzle is now as fast as using raw driver and mapping(or not mapping) results by hand 🙃

interns are just fleshy clankers

@BrandonLuuMD Gaslightmaxxing

Literally just having a delusional golden retriever mindset measurably changes outcomes and physiology. Sleep badly? Convince yourself you're well rested. Stressful day? Convince yourself it's fuel. Failed? Convince yourself it's useful data.

@jxnlco Xursor

Heard that Elon is trying to rename cursor to xcode

@itsandrewgao Xursor

overheard at spacexai: "let's rename it X-code!" "oh wait..." "ok how about Code-X"

@thdxr I think this is going to be an important role. Like in the audio world there is a sound engineer that’s just doing the mixing. Their job isn’t to add to the song but to make sure it comes out right, balance, eq…

@pranaygp @rauchg @workflowsdk Been keeping my eyes on it 😄

@SharingPsyche @rauchg @workflowsdk github.com/vercel/workflo… hoping to get this PR in soon 🙏

The hardest thing about agents and backends is durability. @workflowsdk fixes this. That LLM you're calling *will* go down. That service *will* rate limit you. That database *will* unexpectedly slow down. You *will* get paged 💀 I've been looking for a unicorn for a decade. I wanted the level of reliability of combining stuff like SQS / Kafka / microservices, and I absolutely did not want *that* at the same time 😂 Truly reliable systems like that are notoriously difficult to reason about, to develop locally, to test, to simulate, to deploy… Workflow SDK solves that without compromises. We're doing what Next.js did for the frontend, but for one of the most important problems of the new generation of backend applications. Notably, Workflow SDK has an incredible self-hosting and multi-cloud story from day 0. We've taken amazing lessons from Next.js and poured them into the many Worlds (adapters) you can deploy to. Congrats to Pranay and the Workflow team on a generational ship: vercel.com/blog/a-new-pro…

@shadcn it's giving 2015 (nice job)

Meet Sera. A new foundational style for shadcn/ui. Minimal. Editorial. Typographic. Shaped by Print Design Principles. Available Today. Try on shadcn/create.

@HeyGarrison "tell a story" in the playground

@HeyGarrison We've only used vercel's. You can see if for yourself if you are logged in. vercel.com/ai-gateway/mod…

Is anyone else interested in how the ai gateways perform? Vercel, cf, open router Thinking about doing a time to first token test benchmark

@HeyGarrison chunky bad, it makes the model response come out as half/full sentence at a time. token level stream - or closer to it - feels buttery.

@SharingPsyche do you think the chunky is good or bad?

vercel workflow event signup flow be like: 𝚎𝚡𝚙𝚘𝚛𝚝 𝚊𝚜𝚢𝚗𝚌 𝚏𝚞𝚗𝚌𝚝𝚒𝚘𝚗 𝚊𝚙𝚙𝚛𝚘𝚟𝚊𝚕𝙵𝚕𝚘𝚠(𝚞𝚜𝚎𝚛) { "𝚞𝚜𝚎 𝚠𝚘𝚛𝚔𝚏𝚕𝚘𝚠"; 𝚊𝚠𝚊𝚒𝚝 𝚜𝚎𝚗𝚍𝙿𝚎𝚗𝚍𝚒𝚗𝚐(𝚞𝚜𝚎𝚛); 𝚊𝚠𝚊𝚒𝚝 𝚜𝚕𝚎𝚎𝚙("𝟹𝚑"); 𝚊𝚠𝚊𝚒𝚝 𝚜𝚎𝚗𝚍𝙰𝚙𝚙𝚛𝚘𝚟𝚎𝚍(𝚞𝚜𝚎𝚛); }

@robertcourson if they degrade and then release a ~new amazing~ model (2x more expensive btw) then you'll be eager to make the switch

I’m not usually one to complain, but Claude has been genuinely unusable this past week. I’ll come back when Opus 4.6 gets it's stuff together.

@jayair @kitlangton I thought we were done with slop features? (How can I buy this)

Kit built this, should we ship it? (sound on)

@SheardLuke @cramforce @computesdk Cook faster ;) Before we entrench ourselves in the technical debt of azure blob and e2b

@SharingPsyche @cramforce @computesdk Sounds like you'll like something we're cooking at the moment then 🍳

Vercel Sandboxes are now the fastest sandbox using real VMs as security boundary based on the @computesdk benchmark. The team has been absolutely cooking on this. And the best thing: Because we have a unified Fluid Compute stack across Sandbox, Builds, and Functions these wins are often shared across the stack. On the feature side there is a really exciting roadmap ahead as well. My favorites (all driven by feature requests from our customers): - Persistent sandboxes (in beta, GA immanent) - The fully mutable firewall also becomes fully programmable

@SheardLuke @cramforce @computesdk Chatbot -> user uploads file to chat -> create sandbox if not exist -> mount remote store -> ai has sandbox with user files. Nice for a concept of projects too because multiple sandboxes can mount the same file store (many chats in the same project)

@SheardLuke @cramforce @computesdk Mounting remote storage - using rclone, blobfuse etc. then the compute unit is then mostly ephemeral and you dynamical mount a blob or file store

Can we change the X algo back? It feels like tiktok recently - optimized for slop videos that catch my attention