Discover
The Node (and more) Banter
The Node (and more) Banter
Author: Platformatic
Subscribed: 2Played: 20Subscribe
Share
© Platformatic
Description
The Node (and more) Banter is your weekly dose of unfiltered, unscripted conversations between Luca Maraschi and Matteo Collina.
We explore the edge cases, the anti-patterns, and the things no one puts in the docs. From distributed architecture to platform pitfalls and how enterprises tackle modern development—nothing’s off-limits. It’s not just Node.js®—it’s everything around it, wrapped in sharp banter, war stories, and real-world insight.
The sky’s the limit.
We explore the edge cases, the anti-patterns, and the things no one puts in the docs. From distributed architecture to platform pitfalls and how enterprises tackle modern development—nothing’s off-limits. It’s not just Node.js®—it’s everything around it, wrapped in sharp banter, war stories, and real-world insight.
The sky’s the limit.
86 Episodes
Reverse
Everyone is running AI agents. But how do you coordinate them smoothly?Matteo is out of office for the first time in Banter history, so naturally we replaced him with a team of agents. Luca sits down with Michael and Souren, the founders of AgentGrid, to talk about giving AI agents something they never had: a real interface.Until now, working with agents meant living in a wall of terminals. We talk about why a visual workspace makes agents accessible to far more developers, and what it takes to go from zero to your own software factory (or adopting an existing one), with a team of agents building, testing and shipping side by side.If you’ve ever had five terminals open and no idea which agent did what, this one is for you.
The same Brotli decoder bug hit Node.js, Bun, .NET, Envoy, and Istio at once. Jarred Sumner of Bun reads that as proof that dependencies are over. His view is that rewriting a dependency is now one prompt away, so every project should carry its own code.The Brotli story points the other way. It got one CVE and one coordinated fix, and every affected runtime and proxy was patched within days. Rewrite that decoder a hundred times and the same kind of bug is still there, just in a hundred places nobody is looking at.Matteo Collina, who co-wrote the Node.js fix, and Luca Maraschi push back on the idea that open source dependencies are finished.In this episode, we cover:✅ Why the Brotli response is the system working, not failing✅ Why making every copy of the code different is security through obscurity✅ Why more code means more vulnerabilities, and whether LLMs write safer code✅ Why hardened code, with its years of scars, is the safest code we have✅ How projects with good threat models and triage protect everyone downstreamWhen finding bugs gets cheaper, the answer is to fund and harden shared code, not to scatter it into versions nobody reviews.
Building an MCP server? Here’s what it takes to run one in production on data that actually matters.Luca and Matteo are joined by Roberto Bianchi, Staff Software Engineer at Spendesk, who shipped an MCP server that gives AI assistants access to company spend data: payables, suppliers, budgets, purchase orders.Roberto walks the path from OpenAPI spec to AI tool call: generating type-safe clients so schema changes fail in CI rather than in a broken agent call, reusing existing OAuth, scopes, roles, and tenant boundaries instead of building a second auth stack, shipping retrieval-only first and gating write actions behind a security review, and running internal workflows through the exact same validation and authorization pipeline as external AI calls.The takeaway: an MCP server is just another API surface. With the right tools, treating it like one is what makes it easy.
Deno joined Cloudflare, and with the runtime winding down over the next year, Luca and Matteo look back at what it leaves behind.Deno pioneered web standards on the server and did the hard work of adapting fetch for Node.js, collaborated on Node’s own design decisions, and pushed the whole ecosystem forward.They also give it an honest postmortem: the two wild bets that didn’t survive contact with reality (URL-based package resolution and the “secure by default” permission model), and why trying them was still the right call.
Jarred Sumner’s argument is that for JavaScript and TypeScript to stay relevant in an AI world, where moving a codebase between languages is suddenly cheap, they have to get as fast as Rust or Go.Luca and Matteo work through what that costs. AssemblyScript already solved it by not being TypeScript. Porffor solved it by compiling JavaScript and keeping every check. Bun is trying to sit in the middle, and the middle is where the problems live: TypeScript is not one language but a multiverse of them depending on your tsconfig, and publishing raw source turns one definition per dependency into roughly ten times the work for every checker downstream.There is also the one requirement the TypeScript team gave Node.js when type stripping landed: never run TypeScript from node_modules, because it breaks the ecosystem. Push the idea far enough, and you get types enforced at runtime, which is not JavaScript and not TypeScript. Different language, different runtime.




