node:vfs is in @nodejs core.
Our follow-up covers what shipped in 26.4, 26.9, and 26.10: new mount model, ZIP provider, native addons, node:ffi, SEA support, --vfs-load.
Plus two corrections to our first article.
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.
𝘤𝘢𝘯𝘈𝘤𝘤𝘦𝘴𝘴𝘛𝘰𝘰𝘭 didn't exist in @platformatic/mcp until @Spendesk needed a role check that sees the full request context.
They built it, plus AJV validation, 𝘵𝘳𝘢𝘯𝘴𝘧𝘰𝘳𝘮𝘙𝘰𝘶𝘵𝘦𝘚𝘤𝘩𝘦𝘮𝘢 and 𝘮𝘤𝘱𝘊𝘢𝘭𝘭𝘛𝘰𝘰𝘭, and contributed all of it upstream.
memcached has 3 wire protocols.
Most @nodejs clients still use the oldest one: matching error strings, no way to verify a response is actually yours.
The meta protocol (1.6+) fixes this with opaque tokens. We built ours on it exclusively.
Which one does yours use?
Memcached offers three wire protocols. Reality tells us that most @Node.js clients pick the wrong one, and that exact choice has real consequences.
The classic text protocol relies on string matching for error detection. A single typo or unexpected message can silently break
🎙️ A new Banter episode is coming soon!
@NodeConfEU came back after a year off, new team, new country, and one deliberate decision: 𝐧𝐨𝐭𝐡𝐢𝐧𝐠 𝐚𝐛𝐨𝐮𝐭 𝐀𝐈 𝐨𝐧 𝐭𝐡𝐞 𝐬𝐜𝐡𝐞𝐝𝐮𝐥𝐞.
@lucamaraschi & @matteocollina will debrief the whole thing.