WEBVTT NOTE The Rundown — nextbig.dev daily audio edition, 2026-04-20 1 00:00:00.000 --> 00:00:06.528 Good morning, welcome to Builder's Briefing for April 20th, 2026. I'm Alex, joined as always by Sam, and we've got a packed show today — a breakthrough in client-side AI inference, some critical security news, and a bunch of really nice developer tools. 2 00:00:06.528 --> 00:00:10.191 Yeah, today's lineup is great. And honestly, the lead story has me pretty excited as someone who's been watching WebAssembly evolve for years. 3 00:00:10.191 --> 00:00:19.067 So let's jump right into it. The big story today is a new technique for zero-copy GPU inference from WebAssembly on Apple Silicon. In plain terms, someone figured out how to map Metal GPU buffers directly into Wasm's linear memory space, which eliminates the memory copy overhead that's been the bottleneck for running ML models in the browser. 4 00:00:19.067 --> 00:00:26.368 Right, and what's wild is that memory copying has been this dirty secret of Wasm ML for years. Everyone demos a model running in the browser and it looks cool, but under the hood you're burning time shuttling data between the GPU and the Wasm sandbox. This just... removes that wall. 5 00:00:26.368 --> 00:00:33.051 Exactly. And the proof point is incredible — there's a Show HN project that runs Gemma 4, a multi-billion parameter model, entirely in the browser to generate Excalidraw diagrams from text prompts. The model is three point one gigabytes. No server round-trip. 6 00:00:33.051 --> 00:00:40.404 That's not a toy demo anymore. That's a real application doing real generative work on the client. If you're shipping AI features behind an API today and your users are on Apple devices, you should seriously be prototyping a local-first path. The latency and privacy wins are enormous. 7 00:00:40.404 --> 00:00:47.628 And the portability angle is key — you ship one Wasm artifact and it runs fast on every Apple Silicon device. Mac, iPad, eventually iPhone. The prediction in the briefing is that local-first AI shifts from philosophy to shipping default within six months, and I actually buy that. 8 00:00:47.628 --> 00:00:50.363 I do too. WebGPU is maturing, Apple Silicon dominates developer laptops — the pieces are all in place now. 9 00:00:50.363 --> 00:00:54.698 Sticking with AI — there's a great repo called MiniMind that lets you train a sixty-four million parameter GPT from scratch in about two hours on a single consumer GPU. 10 00:00:54.698 --> 00:01:02.438 That's interesting because it's not about building a production model — it's about understanding. If you're teaching a class or onboarding junior ML engineers, running through the full training pipeline end-to-end in two hours on your own hardware is incredibly valuable. You actually see every step. 11 00:01:02.438 --> 00:01:07.856 And on the design tool front, there's a really heated discussion around Anthropic's Claude Design tool — two hundred eighty-three points, a hundred eighty-five comments on Hacker News. Lots of real UX critique. 12 00:01:07.856 --> 00:01:12.578 Yeah, I skimmed that thread. If you're evaluating AI design tools for your workflow, it's worth reading before you commit. The community is flagging genuine gaps, not just nitpicking. 13 00:01:12.578 --> 00:01:21.376 Alright, let's talk developer tools because there are three that I think pair together beautifully. First, Delta — it replaces your git diff pager with syntax-highlighted, side-by-side diffs. Then Atuin, which syncs your shell history across machines with encrypted SQLite. And Zoxide, a smarter cd command that learns your directory habits. 14 00:01:21.376 --> 00:01:30.277 Oh, I already use Zoxide and it's one of those tools where you wonder how you ever lived without it. But pairing it with Atuin is the real move — you get smart directory jumping and full command history search everywhere. If you're optimizing your terminal this week, install both. It'll shave real seconds off every session, which adds up fast. 15 00:01:30.277 --> 00:01:36.237 There's also Shader Lab, a Show HN tool that gives you a Photoshop-like visual editor for building shaders. Layer-based, no raw GLSL required. If you're doing WebGL or WebGPU work and you're not a shader wizard, this is a big deal. 16 00:01:36.237 --> 00:01:39.462 That pairs nicely with the Wasm-Metal story too, right? The whole WebGPU ecosystem is getting more accessible at every layer. 17 00:01:39.462 --> 00:01:45.680 Great point. Now for launches — the highest engagement repo today is FinceptTerminal, an open-source Bloomberg-style finance terminal. Five point eight thousand stars. It does market analytics, research tools, economic data, all interactive. 18 00:01:45.680 --> 00:01:52.130 If you're in fintech or even just building internal dashboards that need market data, this could save you months. Bloomberg terminals cost twenty-four thousand a year per seat, so an open-source alternative with real community momentum is a big deal. 19 00:01:52.130 --> 00:01:56.852 Also worth flagging — Glance is a self-hosted dashboard that unifies RSS feeds, bookmarks, weather, and service monitoring in one clean interface. Weekend project that pays off daily. 20 00:01:56.852 --> 00:01:59.871 I love those kinds of tools. The ones where you spend two hours on a Saturday and then use them every single morning. 21 00:01:59.871 --> 00:02:03.973 Okay, now the serious stuff. Two security items today, and I want people to actually act on these. First — Vercel confirmed a breach of their internal systems. 22 00:02:03.973 --> 00:02:10.526 Yeah, this is a rotate-first-ask-questions-later situation. If you deploy on Vercel, go rotate your tokens and API keys right now. Audit your deployment logs. Details are still sparse but the platform is so widely used that you just can't afford to wait. 23 00:02:10.526 --> 00:02:16.048 Second one — Notion is leaking editor email addresses on all public pages. If your team uses Notion for public docs, wikis, job postings, anything public-facing, you are exposing internal email addresses right now. 24 00:02:16.048 --> 00:02:21.827 That's a rough one because so many teams use Notion for exactly that. Switch sensitive pages to private immediately, or move your public-facing content to a different platform. This is an active leak, not a theoretical risk. 25 00:02:21.827 --> 00:02:30.006 Quick hits before we wrap — NASA shut off another Voyager 1 instrument to keep the spacecraft alive, which is both heartbreaking and incredible engineering. NIST created lasers that can produce any wavelength on tiny circuits. And there's a great piece on why pause menus in games are surprisingly tricky to engineer. 26 00:02:30.006 --> 00:02:37.798 The pause menu one is so good. You'd think it's trivial, but game devs explain all the edge cases — audio, physics, networking, animation state — it's a rabbit hole. Also, the archive of Byte magazine starting from issue one in nineteen seventy-five? Chef's kiss for anyone who loves computing history. 27 00:02:37.798 --> 00:02:45.770 Alright, here's your takeaway for today. Two things to act on. First, client-side AI inference just crossed the usability threshold. Zero-copy Wasm plus Metal, a three gig model running in-browser — if you're building AI features on Apple platforms, allocate a spike this week to prototype a local-first path. 28 00:02:45.770 --> 00:02:52.117 And second, go handle your security hygiene right now. Rotate your Vercel credentials, audit your Notion public pages for leaked emails. These are platforms people trust implicitly, and that trust is exactly what makes it easy to let things slip. 29 00:02:52.117 --> 00:02:56.762 That's the show for today. All the links are in the briefing. We'll be back tomorrow with more — in the meantime, go build something and maybe rotate a few keys while you're at it. 30 00:02:56.762 --> 00:02:57.1000 Rotate first, code second. See you all tomorrow!