Podcasts about Rust

Wer die Hörbar Rust regelmäßig hört, weiß, dass es uns schon wichtig ist, einen richtig guten Gäste-Mix hinzulegen. Etablierte Schauspielerinnen und Schauspieler, Entertainerinnen und Entertainer, bekannt, noch nicht so bekannt, alt, jung und mittelalt, Autorinnen und Autoren, Musikerinnen, Musiker, die in den analogen oder linearen Medien stattfinden, aber auch Personen, die die Sozialen Medien erfolgreich bespielen und sich dort - im übertragenen Sinne - ihre eigenen Theater aufbauen. So stießen wir vor einiger Zeit schon auf Lina Hella Bookhagen, auch bekannt als Linellaboo. Ihr Podcast heißt "Halb so wild", ihre Videos sind grandiose Veranschaulichungen all dessen, was es überall auf der Welt, insbesondere aber im Berliner Alltag zu erleben gibt. Viel Humor, eine feine Beobachtungsgabe, ein grandioser Umgang mit Sprache und nach verhältnismäßig kurzer Zeit schon insgesamt fast 400.000 Follower auf Tiktok und Instagram - wir freuen uns sehr, sie heute in unserem Studio zu begrüßen. Playlist: Ulli Martin - Gitchy Goomey Labi Siffre - Bless the Telephone Lucilectric - Mädchen The Stranglers - Golden Brown Madsen - Astronaut The Black Eyed Peas - I Gotta Feeling Kettcar - Sommer '89 Declan McKenna - Brazil Diese Podcast-Episode steht unter der Creative Commons Lizenz CC BY-NC-ND 4.0.

You're adding type hints to your Python code, your editor is happy, autocomplete is working great. But then you switch tools and suddenly there are red squiggles everywhere. Who decides what a float annotation actually means? Or whether passing None where an int is expected should be an error? It turns out there's a five-person council dedicated to exactly these questions -- and two brand-new Rust-based type checkers are raising the bar. On this episode, I sit down with three members of the Python Typing Council -- Jelle Zijlstra, Rebecca Chen, and Carl Meyer -- to learn how the type system is governed, where the spec and the type checkers agree and disagree, and get the council's official advice on how much typing is just enough. Episode sponsors Sentry Error Monitoring, Code talkpython26 Agentic AI Course Talk Python Courses Links from the show Guests Carl Meyer: github.com Jelle Zijlstra: jellezijlstra.github.io Rebecca Chen: github.com Typing Council: github.com typing.python.org: typing.python.org details here: github.com ty: docs.astral.sh pyrefly: pyrefly.org conformance test suite project: github.com typeshed: github.com Stub files: mypy.readthedocs.io Pydantic: pydantic.dev Beartype: github.com TOAD AI: github.com PEP 747 – Annotating Type Forms: peps.python.org PEP 724 – Stricter Type Guards: peps.python.org Python Typing Repo (PRs and Issues): github.com Watch this episode on YouTube: youtube.com Episode #539 deep-dive: talkpython.fm/539 Episode transcripts: talkpython.fm Theme Song: Developer Rap

Chris, Andrew, and David welcome special guest Jeff Dickey (jdx), creator of mise, discussing his background rewriting the Heroku CLI from Ruby to Node due to Ruby distribution/sandboxing issues.  The conversation digs into why language CLIs are hard to distribute, the tradeoffs between shims vs PATH-based version switching, why tasks can be the “clean” solution, and Jeff's Rust-first tooling philosophy. They also dive into his other projects: usage (CLI docs/completions), Pitchfork (dev daemon runner that starts/stops services by directory), and fnox/Fort Knox (secrets management with encrypted files or remote stores like 1Password), and a big upcoming shift: pre-compiled (portable) Rubies becoming the default in mise. Press download now!LinksJudoscale- Remote Ruby listener giftJeff Dickey XJeff Dickey (jdx) Blueskymisefnox--usagePitchforkcommuniquéCasey Neistat: NYC's Worst Blizzard in a Decade, hour by hour (YouTube) Chris Oliver X/Twitter Andrew Mason X/Twitter Jason Charnes X/Twitter

Talentgesprek van Jan Prins met Jeroen Ouwehand Wat vraagt het om 34 jaar te floreren aan de top van de internationale advocatuur? In dit openhartige gesprek spreek ik met Jeroen Ouwehand, jarenlang partner bij Clifford Chance en zelfs Global Senior Partner van dit wereldwijde kantoor met duizenden advocaten en tientallen vestigingen. We blikken terug op een indrukwekkende loopbaan – maar vooral op het talent dat daar als rode draad doorheen loopt: stabiliteit onder druk. Volgens zijn TMA-analyse scoort Jeroen uitzonderlijk hoog op stressbestendigheid. En dat zie je overal in zijn verhaal terug. Rust in de storm Waar veel mensen verkrampen bij deadlines, complexe dossiers of miljoenenclaims, lijkt Jeroen juist scherper te worden. Kort geding over twee dagen? Geen probleem. Een slepend internationaal conflict met torenhoge belangen? Laat maar komen. Maar zijn talent gaat verder dan “goed tegen stress kunnen”. Het gaat over comfortabel zijn in onzekerheid. Over kunnen presteren als de druk oploopt. Over beslissingen durven nemen wanneer anderen nog twijfelen. En dat is cruciaal in de wereld van litigation: procederen wanneer het echt misgaat. Conflicten oplossen zonder conflictzoeker te zijn Wat dit gesprek extra interessant maakt: Jeroen ziet zichzelf helemaal niet als iemand die van conflicten houdt. Sterker nog, uit zijn analyse blijkt dat hij privé eerder conflictvermijdend is. Toch bouwde hij zijn carrière op het voeren van juridische gevechten. Hoe dat kan? Omdat hij het conflict niet ziet als strijd om te winnen, maar als probleem om op te lossen. Hard op de inhoud, zacht op de persoon. Procederen als middel om duidelijkheid te creëren. En soms – tegen de wens van de cliënt in – zeggen: “Dit gaan we niet winnen.” Dat vraagt moed. Zeker in een verdienmodel waarin je betaald wordt per uur. Maar juist daar laat zijn stabiliteit zich zien: niet meegaan in emotie, niet bezwijken onder druk van de cliënt, maar het grotere plaatje blijven zien. Van jonge advocaat tot wereldwijd leider We spreken uitgebreid over zijn verkiezing tot Global Senior Partner van Clifford Chance – een positie vergelijkbaar met voorzitter van de raad van toezicht. Een Nederlander aan het hoofd van een van oorsprong Londens kantoor: dat is geen vanzelfsprekendheid. Zijn campagne voerde hem langs Hongkong, New York, Frankfurt en Londen. Debatten, stemrondes, internationale politiek. En ook hier zie je zijn talent terug: kalm blijven in een bijna presidentiële verkiezingsstrijd. Hij won. En verloor vier jaar later de herverkiezing. Ook daarover spreekt hij opmerkelijk nuchter. Teleurgesteld? Natuurlijk. Maar verbitterd? Integendeel. Hij reflecteert eerlijk op culturele verschillen tussen Nederland en Engeland, op directheid versus diplomatie, en op het spanningsveld tussen progressieve ambities en een conservatievere internationale realiteit. Ondernemerschap in toga Wat mij persoonlijk verraste, is hoe ondernemend hij altijd is geweest. In de begintijd van het internet was hij een van de eerste advocaten die zich stortte op techbedrijven en startups. Hij zag de energie, de toekomst, de kansen. Zelfs het idee van “sweat for equity” – werken in ruil voor aandelen – bracht hij al vroeg in bij zijn kantoor. Misschien te vroeg. Maar het typeert zijn nieuwsgierigheid en lef. Ook hier weer die combinatie: stabiliteit én ondernemingszin. Rust onder druk, maar wél in beweging. AI en de toekomst van het vak We eindigen bij een actueel thema: kunstmatige intelligentie. Wat betekent AI voor de advocatuur? Gaat het het vak uithollen of juist versterken? Jeroen kiest geen defensieve houding. Hij ziet AI als een krachtig hulpmiddel, maar benadrukt iets fundamenteels: je moet zelf blijven denken. Zelf analyseren. Zelf begrijpen wat er staat. Anders verlies je het ambacht. En misschien is dat wel de kern van dit hele gesprek. Stabiliteit betekent niet stilstand. Het betekent stevig staan terwijl de wereld verandert. Een gesprek over leiderschap, internationale politiek, ondernemerschap, verliezen zonder bitterheid en presteren onder maximale druk. Benieuwd hoe het is om op het hoogste niveau beslissingen te nemen terwijl de hele organisatie meekijkt? Luister dan deze aflevering van Talentgesprekken. Het talent achter de prestatie – dit keer: stabiel blijven waar anderen wankelen.

Mike on LinkedIn Coder Radio on Discord Mike's Oryx Review Alice Alice Jumpstart Offer

In this episode of Screaming in the Cloud, host Corey Quinn sits down with Roi Lipman, CTO and co-founder of Falco DB, to unpack the evolving role of graph databases in a world overflowing with data stores. Roi shares his journey from building RedisGraph at Redis to spinning it out into Falco DB, along with his enduring love of the C programming language (dad jokes included). The conversation explores why graph databases remain niche, but powerful, especially for pathfinding problems like supply chains and access management, how vector search became a feature rather than a standalone database, and what AI-assisted development means for modern engineering. Along the way, they tackle open source sustainability, Rust rewrites, AI-generated pull request chaos, and the looming question of where the next generation of senior engineers will come from.Highlights: (00:00) C Language(00:27) Welcome(01:18) Database Landscape Overview(03:17) Why Graph Databases Matter(07:25) AI Built Apps and Data Choices(10:29) How FalcoDB Fits In(12:20) Vector Search as a Feature(16:48) FalcoDB Origin Story(19:54) Open Source Business and Rust Rewrite(25:23) Toy Graph Problems and Closing ThoughtsSponsored by: duckbillhq.com

Will Madden joins the podcast to talk about Prisma Next and the evolution from Prisma 7, including the decision to migrate away from Rust, ship the core through WebAssembly, and move toward a fully TypeScript ORM. The conversation dives into how modern workflows like agentic coding change the role of an ORM and why tools still matter even when agents can write SQL queries directly. We discuss how feedback loops, guardrails, and the TypeScript type system help prevent errors, along with the new query builder, query linter, and middleware layer that analyze queries using an abstract syntax tree. The episode also covers new database capabilities including Postgres support, upcoming Mongo support, and extensions like PG Vector, enabling vector columns and cosine distance similarity search. You'll also learn about new patterns such as collection methods, scopes, and composable database extensions, plus tooling like driver adapters, a potential compatibility layer, and safeguards like lint rules and a performance budget middleware designed to catch expensive queries before they run. Resources The Next Evolution of Prisma ORM: https://www.prisma.io/blog/the-next-evolution-of-prisma-orm We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Fill out our listener survey! https://t.co/oKVAEXipxu Let us know by sending an email to our producer, Elizabeth, at elizabeth.becz@logrocket.com, or tweet at us at PodRocketPod. Check out our newsletter! https://blog.logrocket.com/the-replay-newsletter/ Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form, and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. Chapters 00:00 Introduction 01:00 Prisma Seven and the Move Away from Rust 02:20 Missing Features and Mongo Support 03:00 Why Prisma Started Rebuilding the Core 04:00 Community Sentiment and Developer Feedback 05:20 Rethinking ORMs in the AI and Agentic Coding Era 06:45 Why Agents Still Need ORMs 07:30 Feedback Loops and Guardrails for SQL 08:30 Type Safety and the First Layer of Query Validation 09:30 Query Linter and Middleware Architecture 11:00 Runtime Validation and Query Errors 12:30 Configuring Lint Rules and Guardrails 14:00 Designing ORMs for Humans and Agents 15:30 Collection Methods and ActiveRecord-style Scopes 17:00 Reusable Queries and Domain Vocabulary 18:30 Query Composition and Flexibility 19:00 Performance Guardrails and Query Budget Middleware 20:30 Debugging ORM Performance Issues 21:00 Query Telemetry and Request Tracing 22:30 Prisma Next Extensibility and Database Plugins 23:00 Using PGVector and Vector Search 24:00 Database Drivers and Backend Architecture 25:00 Native Mongo Support in Prisma Next 26:00 Community Extensions and Middleware Ecosystem 27:00 Runtime Schema Validation Use Cases 28:00 Writing Custom Query Validation Rules 29:00 Migration Paths from Prisma Seven 30:30 Compatibility Layers vs Parallel Systems 32:00 Prisma Next Roadmap and Timeline 34:30 What Developers Will Be Most Excited About 35:30 Final Thoughts and Community Feedback

Je wil afvallen. Dus je gaat beter opletten, strenger doen met eten, jezelf beter in de hand proberen te houden.Logisch. Alleen werkt het niet. En in deze aflevering leg ik uit waarom.Het probleem zit niet in het eten. Het zit in wat er al veel eerder die dag is gebeurd, en in wat er ná het overeten komt. Die twee dingen samen houden een cirkel in stand waar veel vrouwen jarenlang niet uitkomen, hoe hard ze ook proberen.Overeten gaat niet over eten. Dit is waar het wél over gaat.Stuur me een DM met het woord RUST als je op de wachtlijst wil voor Rust Rondom Eten. De volgende ronde start in april.InstagramWerk met mij

Rust is everywhere - in your tools and in your stack - and has been ranked as the most admired programming language for over a decade. Join us for a quick chat as we unpack why more Python developers are turning their attention to Rust, and why now might be the right time for you to do the same.If you've been seeing Rust pop up at work, on LinkedIn, or in your favourite Python libraries, this episode will help you understand what's going on, and whether learning Rust could give you a real edge as a Python developer.To find out more about how we help Python developers with Rust, check out the following:Rust exercise platform: http://rustplatform.com/via/pybitesRust cohort: http://scriptertorust.comArticle Julian mentioned: https://pybit.es/articles/coding-can-be-super-lonely/___

Your AI agent just ordered 5 pizzas, and you couldn't stop it... George Zeng, CPO at NEAR, joins The Rollup to discuss the security flaws in open-source AI agents, why Iron Claw was rebuilt from the ground up in Rust, and what it takes to actually trust an agent with your personal data.George Zeng is one of the leading Layer 1 blockchains focused on user-owned AI and decentralized applications. NEAR recently launched Iron Claw, a secure AI agent framework built in Rust with sandboxed tool access, prompt injection protection, and confidential inference designed to give users the confidence to hand agents real-world permissions.The Rollup is the convergence of legacy finance and DeFi, bringing you face-to-face with the leaders of Neo Finance.Timestamps:00:00 Intro01:19 Iron Claw Launch & Setup01:50 Open Claw vs. Iron Claw03:55 Iron Claw Origin Story05:13 AI Agents Going Rogue05:28 infiniFi, Relay Ads06:03 Model vs. Framework Security07:13 Prompt Injection Prevention07:50 Agent-To-Agent Data Theft08:19 Plans & Pricing09:46 The $150 Pizza Incident12:11 Hibachi Ad12:46 No Terminal Needed16:28 Why Security Is The Key Differentiator18:11 The Perfect AI Assistant Analogy19:01 NEAR Intents & Real-World TransactionsWebsite: https://therollup.co/Spotify: https://open.spotify.com/show/1P6ZeYd...Podcast: https://therollup.co/category/podcastFollow us on X: https://www.x.com/therollupcoFollow Rob on X: https://www.x.com/robbie_rollupFollow Andy on X: https://www.x.com/ayyyeandyJoin our TG group: https://t.me/+TsM1CRpWFgk1NGZhThe Rollup Disclosures: https://goodidea.ventures

Links to research used for the discussion1st resource:https://extension.usu.edu/planthealth/ipm/notes_ag/hemp-nutrient-deficiencies2nd resource: https://www.mdpi.com/2076-3417/9/20/4432This week host @Jackgreenstalk (aka @Jack_Greenstalk on X/instagram backup account) [or contact via email: JackGreenstalk47@gmail.com] is joined by panel with , @spartangrown on instagram or X f.k.a. Twitter at https://x.com/grown43626 or email spartangrown@gmail.com for contacting spartan outside social media, any alternate profiles on other social medias using spartan's name, and photos are not actually spartan grown be aware, @NoahtheeGrowa on instagram and @TheAmericanOne on youtube aka @theamericanone_with_achenes on instagram who's amy aces can be found at amyaces.com on instagram, .... This week we missed Rust Brandon of @fulcrop.sciences / fulcrop.ceo regained @Rust.Brandon instagram page, and products can be found at bokashiearthworks.com , Matthew Gates aka @SynchAngel on instagram and twitter @Zenthanol on youtube who offers IPM direct chat for $1 a month on patreon.com/zenthanol , @drmjcoco from cocoforcannabis.com as well as youtube where he tests and reviews grow lights and has grow tutorials and @drmjcoco on instagram and @ATG Acres Aaron The Grower aka @atgacres his products can be found at atgacres.com view his instagram to find out details about drops!

Josh talks to Sylvestre Ledru about the Rust coreutils project. We've been using GNU coreutils for decades now, and the goal of Rust coreutils is to rewrite these utilities in Rust. The primary reason isn't security, it's to modernize the code and attract new contributors. Sylvestre discusses with quite pleasant relationship with the GNU coreutils developers, some of the challenges in the project. What Ubuntu using this by default meant, and also gives us some things to watch for in the future. It's a super fun discussion about why Rust is not only awesome, but also the future. The show notes and blog post for this episode can be found at https://opensourcesecurity.io/2026/2026-03-rust-coreutils-sylvestre-ledru/

¿Es posible tener una Stream Deck profesional en Linux por una fracción de lo que cuesta la marca líder? La respuesta es un rotundo sí, y en este episodio te cuento cómo lo he logrado. Muchos de nosotros hemos mirado con recelo los dispositivos de 150 euros , pensando que no dejan de ser una "botonera bonita". Yo mismo tenía ese prejuicio , pero tras probar las alternativas económicas y, sobre todo, descubrir el potencial del software OpenDeck, mi visión ha cambiado por completo. ¿Qué vas a aprender en este episodio?Adiós al hardware prohibitivo: Analizamos opciones como Soomfon y Mars Gaming que ofrecen la misma funcionalidad que Elgato por apenas 50€. OpenDeck, la salvación del Linuxero: Descubre esta herramienta de código abierto programada en Rust que permite gestionar cualquier Stream Controller en Linux, Windows y macOS. Compatibilidad total: Cómo utilizar los plugins del ecosistema de Elgato directamente en tu software libre. Tu móvil como mando: Te explico cómo usar Tacto para convertir cualquier Android en una Stream Deck sin gastar un céntimo. Integración avanzada: Mi setup personal con OBS para controlar grabaciones y mi configuración con el gestor de ventanas Niri usando potenciómetros para el scroll y cambio de escritorio. Contenido detallado:00:00:00 Introducción y el teclado de 15 euros00:01:48 Mis prejuicios con las Stream Deck00:03:10 La magia de los botones dinámicos y LCD00:05:31 OpenDeck: El corazón de tu Stream Deck en Linux00:06:41 Alternativas económicas: Soomfon y Mars Gaming00:08:43 ¿Por qué elegí el modelo con potenciómetros?00:10:47 OpenDeck a fondo: Plugins y compatibilidad00:13:37 Personalización y Multi OBS Controller00:16:10 La opción gratuita: Convierte tu Android en un controlador con Tacto00:18:55 Mi flujo de trabajo: Integración con OBS y el gestor Niri00:21:51 Despedida y conclusiones finalesSi alguna vez has querido automatizar tus tareas, lanzar sonidos en tus podcasts o simplemente controlar tu escritorio con un giro de rueda, este episodio te dará todas las claves técnicas y económicas para hacerlo posible bajo Linux. No olvides dejar tu valoración en Spotify o Apple Podcasts si te ha gustado el contenido. ¡Disfruta del episodio! Más información, enlaces y notas en https://atareao.es/podcast/775

John and Marc discuss branding for private equity and its role in acquisitions. Marc discusses his background in economics and his passion for finance and marketing, emphasizing his role in explaining complex financial concepts and aligning internal and external messaging for businesses. He highlights his focus on private equity and their portfolio companies. He states private equityis moving away from quick flips to a more sustainable approach of nurturing companies for long-term growth through acquisitions and mergers.He explains how branding is often an afterthought in private equity transactions but emphasizes its importance in managing "acquisition turbulence" and aligning employees with new ownership. He shares an example of helping an optics company merge five entities into one by redesigning their brand, which resulted in a stronger market position and clearer messaging. Marc highlights that effective branding can lead to reduced acquisition costs, increased revenue growth, and improved employee alignment, while also enhancing investor perception.We cover the power of branding, using examples like Goodyear and Michelin to illustrate how strong branding transcends product categories and builds trust through clear messaging and consistent storytelling. Clarity over cleverness in brand messaging, particularly in taglines is important. He criticizes vague taglines like "Bright Minds, Brighter Outcomes" and advocates for brands to ask their audiences what they stand for. All in all, a fascinating discussion.John MartinkaJessica MartinkaContact us via either website or give us a call and be sure to check out our videos https://nokomisadvisory.com/https://www.martinkaconsulting.com/ https://www.gddpodcast.buzzsprout.comhttps://www.youtube.com/c/JohnAMartinka/videos 425-515-4903

This show starts with an Android review, looking at Jonathan's newest tablet. It also covers the coming Android apocalypse, the age verification legislation, and the sudo-rs asterisk fight. Mesa is grappling with AI, Ardour has a couple of point releases, and Gnome is redirecting traffic to GitHub. Fedora has a new mobile experiment in PocketBlue, and the 0 A.D. game has a stable release. For tips we have PyNetscan for IP scanning, snapper for BTRFS snapshots, mediainfo for media file investigations, and espanso for automatic text expansion. Find the show notes at https://bit.ly/3N9X3ys and enjoy! Host: Jonathan Bennett Co-Hosts: Ken McDonald, Rob Campbell, and Jeff Massie Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord. Sponsor: bitwarden.com/twit

Join us in Clean Biz Network! https://www.cleanbiznetwork.app/Get your Cleaning Business Automated! Visit https://cleanbizuniversity.com/automa...Join this channel to get access to perks:   / @ajsimmonsonline  Schedule a 1 on 1 Consultation: https://calendly.com/ajsimmonsLet my lead generation company to set bid appointments for you! Click here https://www.cleanbizcrm.com/leadgener...Follow: @AjSimmonsOnline on Instagram   / ajsimmonsonline  Need Business Insurance? Click this link https://nextinsurance.sjv.io/Ea23K9Need Business Credit? Apply at this linkhttps://americanexpress.com/en-us/ref...Thank you for watching, subscribing, liking, sharing, and commenting!!!!

This show starts with an Android review, looking at Jonathan's newest tablet. It also covers the coming Android apocalypse, the age verification legislation, and the sudo-rs asterisk fight. Mesa is grappling with AI, Ardour has a couple of point releases, and Gnome is redirecting traffic to GitHub. Fedora has a new mobile experiment in PocketBlue, and the 0 A.D. game has a stable release. For tips we have PyNetscan for IP scanning, snapper for BTRFS snapshots, mediainfo for media file investigations, and espanso for automatic text expansion. Find the show notes at https://bit.ly/3N9X3ys and enjoy! Host: Jonathan Bennett Co-Hosts: Ken McDonald, Rob Campbell, and Jeff Massie Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord. Sponsor: bitwarden.com/twit

Strategic energy agreements between Google, Xcel Energy, and TotalEnergies designed to power expanding data center operations with carbon-free electricity. A central component of this initiative is the deployment of a 300 MW iron-air battery system in Minnesota developed by Form Energy, a technology capable of storing renewable power for up to 100 hours. This long-duration storage solution is paired with significant new wind and solar capacity to ensure grid reliability and support state-level decarbonization goals. Additionally, Google has secured a 1 GW solar deal in Texas and is exploring small modular nuclear reactors to meet the immense electricity demands of artificial intelligence. To support these projects, Form Energy is expanding its high-volume manufacturing facility at a former steel mill in West Virginia. The documents also include financial disclosures and risk warnings from the involved corporations, alongside technical debates regarding the efficiency and economic viability of iron-air batteries compared to lithium-ion standards.

Utah Puck Report host Jay Stevens

Utah Puck Report host Jay Stevens President Trump putting together roundtable to fix college athletics Whole World News

Bryan Cantrill is the co-founder and CTO of Oxide Computer Company. We discuss why the biggest cloud providers don't use off the shelf hardware, how scaling data centers at samsung's scale exposed problems with hard drive firmware, how the values of NodeJS are in conflict with robust systems, choosing Rust, and the benefits of Oxide Computer's rack scale approach. This is an extended version of an interview posted on Software Engineering Radio. Related links Oxide Computer Oxide and Friends Illumos Platform as a Reflection of Values RFD 26 bhyve CockroachDB Heterogeneous Computing with Raja Koduri Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Bryan Cantrill. He's the co-founder and CTO of Oxide computer company, and he was previously the CTO of Joyent and he also co-authored the DTrace Tracing framework while he was at Sun Microsystems. [00:00:14] Jeremy: Bryan, welcome to Software Engineering radio. [00:00:17] Bryan: Uh, awesome. Thanks for having me. It's great to be here. [00:00:20] Jeremy: You're the CTO of a company that makes computers. But I think before we get into that, a lot of people who built software, now that the actual computer is abstracted away, they're using AWS or they're using some kind of cloud service. So I thought we could start by talking about, data centers. [00:00:41] Jeremy: 'cause you were. Previously working at Joyent, and I believe you got bought by Samsung and you've previously talked about how you had to figure out, how do I run things at Samsung's scale. So how, how, how was your experience with that? What, what were the challenges there? Samsung scale and migrating off the cloud [00:01:01] Bryan: Yeah, I mean, so at Joyent, and so Joyent was a cloud computing pioneer. Uh, we competed with the likes of AWS and then later GCP and Azure. Uh, and we, I mean, we were operating at a scale, right? We had a bunch of machines, a bunch of dcs, but ultimately we know we were a VC backed company and, you know, a small company by the standards of, certainly by Samsung standards. [00:01:25] Bryan: And so when, when Samsung bought the company, I mean, the reason by the way that Samsung bought Joyent is Samsung's. Cloud Bill was, uh, let's just say it was extremely large. They were spending an enormous amount of money every year on, on the public cloud. And they realized that in order to secure their fate economically, they had to be running on their own infrastructure. [00:01:51] Bryan: It did not make sense. And there's not, was not really a product that Samsung could go buy that would give them that on-prem cloud. Uh, I mean in that, in that regard, like the state of the market was really no different. And so they went looking for a company, uh, and bought, bought Joyent. And when we were on the inside of Samsung. [00:02:11] Bryan: That we learned about Samsung scale. And Samsung loves to talk about Samsung scale. And I gotta tell you, it is more than just chest thumping. Like Samsung Scale really is, I mean, just the, the sheer, the number of devices, the number of customers, just this absolute size. they really wanted to take us out to, to levels of scale, certainly that we had not seen. [00:02:31] Bryan: The reason for buying Joyent was to be able to stand up on their own infrastructure so that we were gonna go buy, we did go buy a bunch of hardware. Problems with server hardware at scale [00:02:40] Bryan: And I remember just thinking, God, I hope Dell is somehow magically better. I hope the problems that we have seen in the small, we just. You know, I just remember hoping and hope is hope. It was of course, a terrible strategy and it was a terrible strategy here too. Uh, and the we that the problems that we saw at the large were, and when you scale out the problems that you see kind of once or twice, you now see all the time and they become absolutely debilitating. [00:03:12] Bryan: And we saw a whole series of really debilitating problems. I mean, many ways, like comically debilitating, uh, in terms of, of showing just how bad the state-of-the-art. Yes. And we had, I mean, it should be said, we had great software and great software expertise, um, and we were controlling our own system software. [00:03:35] Bryan: But even controlling your own system software, your own host OS, your own control plane, which is what we had at Joyent, ultimately, you're pretty limited. You go, I mean, you got the problems that you can obviously solve, the ones that are in your own software, but the problems that are beneath you, the, the problems that are in the hardware platform, the problems that are in the componentry beneath you become the problems that are in the firmware. IO latency due to hard drive firmware [00:04:00] Bryan: Those problems become unresolvable and they are deeply, deeply frustrating. Um, and we just saw a bunch of 'em again, they were. Comical in retrospect, and I'll give you like a, a couple of concrete examples just to give, give you an idea of what kinda what you're looking at. one of the, our data centers had really pathological IO latency. [00:04:23] Bryan: we had a very, uh, database heavy workload. And this was kind of right at the period where you were still deploying on rotating media on hard drives. So this is like, so. An all flash buy did not make economic sense when we did this in, in 2016. This probably, it'd be interesting to know like when was the, the kind of the last time that that actual hard drives made sense? [00:04:50] Bryan: 'cause I feel this was close to it. So we had a, a bunch of, of a pathological IO problems, but we had one data center in which the outliers were actually quite a bit worse and there was so much going on in that system. It took us a long time to figure out like why. And because when, when you, when you're io when you're seeing worse io I mean you're naturally, you wanna understand like what's the workload doing? [00:05:14] Bryan: You're trying to take a first principles approach. What's the workload doing? So this is a very intensive database workload to support the, the object storage system that we had built called Manta. And that the, the metadata tier was stored and uh, was we were using Postgres for that. And that was just getting absolutely slaughtered. [00:05:34] Bryan: Um, and ultimately very IO bound with these kind of pathological IO latencies. Uh, and as we, you know, trying to like peel away the layers to figure out what was going on. And I finally had this thing. So it's like, okay, we are seeing at the, at the device layer, at the at, at the disc layer, we are seeing pathological outliers in this data center that we're not seeing anywhere else. [00:06:00] Bryan: And that does not make any sense. And the thought occurred to me. I'm like, well, maybe we are. Do we have like different. Different rev of firmware on our HGST drives, HGST. Now part of WD Western Digital were the drives that we had everywhere. And, um, so maybe we had a different, maybe I had a firmware bug. [00:06:20] Bryan: I, this would not be the first time in my life at all that I would have a drive firmware issue. Uh, and I went to go pull the firmware, rev, and I'm like, Toshiba makes hard drives? So we had, I mean. I had no idea that Toshiba even made hard drives, let alone that they were our, they were in our data center. [00:06:38] Bryan: I'm like, what is this? And as it turns out, and this is, you know, part of the, the challenge when you don't have an integrated system, which not to pick on them, but Dell doesn't, and what Dell would routinely put just sub make substitutes, and they make substitutes that they, you know, it's kind of like you're going to like, I don't know, Instacart or whatever, and they're out of the thing that you want. [00:07:03] Bryan: So, you know, you're, someone makes a substitute and like sometimes that's okay, but it's really not okay in a data center. And you really want to develop and validate a, an end-to-end integrated system. And in this case, like Toshiba doesn't, I mean, Toshiba does make hard drives, but they are a, or the data they did, uh, they basically were, uh, not competitive and they were not competitive in part for the reasons that we were discovering. [00:07:29] Bryan: They had really serious firmware issues. So the, these were drives that would just simply stop a, a stop acknowledging any reads from the order of 2,700 milliseconds. Long time, 2.7 seconds. Um. And that was a, it was a drive firmware issue, but it was highlighted like a much deeper issue, which was the simple lack of control that we had over our own destiny. [00:07:53] Bryan: Um, and it's an, it's, it's an example among many where Dell is making a decision. That lowers the cost of what they are providing you marginally, but it is then giving you a system that they shouldn't have any confidence in because it's not one that they've actually designed and they leave it to the customer, the end user, to make these discoveries. [00:08:18] Bryan: And these things happen up and down the stack. And for every, for whether it's, and, and not just to pick on Dell because it's, it's true for HPE, it's true for super micro, uh, it's true for your switch vendors. It's, it's true for storage vendors where the, the, the, the one that is left actually integrating these things and trying to make the the whole thing work is the end user sitting in their data center. AWS / Google are not buying off the shelf hardware but you can't use it [00:08:42] Bryan: There's not a product that they can buy that gives them elastic infrastructure, a cloud in their own DC The, the product that you buy is the public cloud. Like when you go in the public cloud, you don't worry about the stuff because that it's, it's AWS's issue or it's GCP's issue. And they are the ones that get this to ground. [00:09:02] Bryan: And they, and this was kind of, you know, the eye-opening moment. Not a surprise. Uh, they are not Dell customers. They're not HPE customers. They're not super micro customers. They have designed their own machines. And to varying degrees, depending on which one you're looking at. But they've taken the clean sheet of paper and the frustration that we had kind of at Joyent and beginning to wonder and then Samsung and kind of wondering what was next, uh, is that, that what they built was not available for purchase in the data center. [00:09:35] Bryan: You could only rent it in the public cloud. And our big belief is that public cloud computing is a really important revolution in infrastructure. Doesn't feel like a different, a deep thought, but cloud computing is a really important revolution. It shouldn't only be available to rent. You should be able to actually buy it. [00:09:53] Bryan: And there are a bunch of reasons for doing that. Uh, one in the one we we saw at Samsung is economics, which I think is still the dominant reason where it just does not make sense to rent all of your compute in perpetuity. But there are other reasons too. There's security, there's risk management, there's latency. [00:10:07] Bryan: There are a bunch of reasons why one might wanna to own one's own infrastructure. But, uh, that was very much the, the, so the, the genesis for oxide was coming out of this very painful experience and a painful experience that, because, I mean, a long answer to your question about like what was it like to be at Samsung scale? [00:10:27] Bryan: Those are the kinds of things that we, I mean, in our other data centers, we didn't have Toshiba drives. We only had the HDSC drives, but it's only when you get to this larger scale that you begin to see some of these pathologies. But these pathologies then are really debilitating in terms of those who are trying to develop a service on top of them. [00:10:45] Bryan: So it was, it was very educational in, in that regard. And you're very grateful for the experience at Samsung in terms of opening our eyes to the challenge of running at that kind of scale. [00:10:57] Jeremy: Yeah, because I, I think as software engineers, a lot of times we, we treat the hardware as a, as a given where, [00:11:08] Bryan: Yeah. [00:11:08] Bryan: Yeah. There's software in chard drives [00:11:09] Jeremy: It sounds like in, in this case, I mean, maybe the issue is not so much that. Dell or HP as a company doesn't own every single piece that they're providing you, but rather the fact that they're swapping pieces in and out without advertising them, and then when it becomes a problem, they're not necessarily willing to, to deal with the, the consequences of that. [00:11:34] Bryan: They just don't know. I mean, I think they just genuinely don't know. I mean, I think that they, it's not like they're making a deliberate decision to kind of ship garbage. It's just that they are making, I mean, I think it's exactly what you said about like, not thinking about the hardware. It's like, what's a hard drive? [00:11:47] Bryan: Like what's it, I mean, it's a hard drive. It's got the same specs as this other hard drive and Intel. You know, it's a little bit cheaper, so why not? It's like, well, like there's some reasons why not, and one of the reasons why not is like, uh, even a hard drive, whether it's rotating media or, or flash, like that's not just hardware. [00:12:05] Bryan: There's software in there. And that the software's like not the same. I mean, there are components where it's like, there's actually, whether, you know, if, if you're looking at like a resistor or a capacitor or something like this Yeah. If you've got two, two parts that are within the same tolerance. Yeah. [00:12:19] Bryan: Like sure. Maybe, although even the EEs I think would be, would be, uh, objecting that a little bit. But the, the, the more complicated you get, and certainly once you get to the, the, the, the kind of the hardware that we think of like a, a, a microprocessor, a a network interface card, a a, a hard driver, an NVME drive. [00:12:38] Bryan: Those things are super complicated and there's a whole bunch of software inside of those things, the firmware, and that's the stuff that, that you can't, I mean, you say that software engineers don't think about that. It's like you, no one can really think about that because it's proprietary that's kinda welded shut and you've got this abstraction into it. [00:12:55] Bryan: But the, the way that thing operates is very core to how the thing in aggregate will behave. And I think that you, the, the kind of, the, the fundamental difference between Oxide's approach and the approach that you get at a Dell HP Supermicro, wherever, is really thinking holistically in terms of hardware and software together in a system that, that ultimately delivers cloud computing to a user. [00:13:22] Bryan: And there's a lot of software at many, many, many, many different layers. And it's very important to think about, about that software and that hardware holistically as a single system. [00:13:34] Jeremy: And during that time at Joyent, when you experienced some of these issues, was it more of a case of you didn't have enough servers experiencing this? So if it would happen, you might say like, well, this one's not working, so maybe we'll just replace the hardware. What, what was the thought process when you were working at that smaller scale and, and how did these issues affect you? UEFI / Baseboard Management Controller [00:13:58] Bryan: Yeah, at the smaller scale, you, uh, you see fewer of them, right? You just see it's like, okay, we, you know, what you might see is like, that's weird. We kinda saw this in one machine versus seeing it in a hundred or a thousand or 10,000. Um, so you just, you just see them, uh, less frequently as a result, they are less debilitating. [00:14:16] Bryan: Um, I, I think that it's, when you go to that larger scale, those things that become, that were unusual now become routine and they become debilitating. Um, so it, it really is in many regards a function of scale. Uh, and then I think it was also, you know, it was a little bit dispiriting that kind of the substrate we were building on really had not improved. [00:14:39] Bryan: Um, and if you look at, you know, the, if you buy a computer server, buy an x86 server. There is a very low layer of firmware, the BIOS, the basic input output system, the UEFI BIOS, and this is like an abstraction layer that has, has existed since the eighties and hasn't really meaningfully improved. Um, the, the kind of the transition to UEFI happened with, I mean, I, I ironically with Itanium, um, you know, two decades ago. [00:15:08] Bryan: but beyond that, like this low layer, this lowest layer of platform enablement software is really only impeding the operability of the system. Um, you look at the baseboard management controller, which is the kind of the computer within the computer, there is a, uh, there is an element in the machine that needs to handle environmentals, that needs to handle, uh, operate the fans and so on. [00:15:31] Bryan: Uh, and that traditionally has this, the space board management controller, and that architecturally just hasn't improved in the last two decades. And, you know, that's, it's a proprietary piece of silicon. Generally from a company that no one's ever heard of called a Speed, uh, which has to be, is written all on caps, so I guess it needs to be screamed. [00:15:50] Bryan: Um, a speed has a proprietary part that has a, there is a root password infamously there, is there, the root password is encoded effectively in silicon. So, uh, which is just, and for, um, anyone who kind of goes deep into these things, like, oh my God, are you kidding me? Um, when we first started oxide, the wifi password was a fraction of the a speed root password for the bmc. [00:16:16] Bryan: It's kinda like a little, little BMC humor. Um, but those things, it was just dispiriting that, that the, the state-of-the-art was still basically personal computers running in the data center. Um, and that's part of what, what was the motivation for doing something new? [00:16:32] Jeremy: And for the people using these systems, whether it's the baseboard management controller or it's the The BIOS or UF UEFI component, what are the actual problems that people are seeing seen? Security vulnerabilities and poor practices in the BMC [00:16:51] Bryan: Oh man, I, the, you are going to have like some fraction of your listeners, maybe a big fraction where like, yeah, like what are the problems? That's a good question. And then you're gonna have the people that actually deal with these things who are, did like their heads already hit the desk being like, what are the problems? [00:17:06] Bryan: Like what are the non problems? Like what, what works? Actually, that's like a shorter answer. Um, I mean, there are so many problems and a lot of it is just like, I mean, there are problems just architecturally these things are just so, I mean, and you could, they're the problems spread to the horizon, so you can kind of start wherever you want. [00:17:24] Bryan: But I mean, as like, as a really concrete example. Okay, so the, the BMCs that, that the computer within the computer that needs to be on its own network. So you now have like not one network, you got two networks that, and that network, by the way, it, that's the network that you're gonna log into to like reset the machine when it's otherwise unresponsive. [00:17:44] Bryan: So that going into the BMC, you can are, you're able to control the entire machine. Well it's like, alright, so now I've got a second net network that I need to manage. What is running on the BMC? Well, it's running some. Ancient, ancient version of Linux it that you got. It's like, well how do I, how do I patch that? [00:18:02] Bryan: How do I like manage the vulnerabilities with that? Because if someone is able to root your BMC, they control the system. So it's like, this is not you've, and now you've gotta go deal with all of the operational hair around that. How do you upgrade that system updating the BMC? I mean, it's like you've got this like second shadow bad infrastructure that you have to go manage. [00:18:23] Bryan: Generally not open source. There's something called open BMC, um, which, um, you people use to varying degrees, but you're generally stuck with the proprietary BMC, so you're generally stuck with, with iLO from HPE or iDRAC from Dell or, or, uh, the, uh, su super micros, BMC, that H-P-B-M-C, and you are, uh, it is just excruciating pain. [00:18:49] Bryan: Um, and that this is assuming that by the way, that everything is behaving correctly. The, the problem is that these things often don't behave correctly, and then the consequence of them not behaving correctly. It's really dire because it's at that lowest layer of the system. So, I mean, I'll give you a concrete example. [00:19:07] Bryan: a customer of theirs reported to me, so I won't disclose the vendor, but let's just say that a well-known vendor had an issue with their, their temperature sensors were broken. Um, and the thing would always read basically the wrong value. So it was the BMC that had to like, invent its own ki a different kind of thermal control loop. [00:19:28] Bryan: And it would index on the, on the, the, the, the actual inrush current. It would, they would look at that at the current that's going into the CPU to adjust the fan speed. That's a great example of something like that's a, that's an interesting idea. That doesn't work. 'cause that's actually not the temperature. [00:19:45] Bryan: So like that software would crank the fans whenever you had an inrush of current and this customer had a workload that would spike the current and by it, when it would spike the current, the, the, the fans would kick up and then they would slowly degrade over time. Well, this workload was spiking the current faster than the fans would degrade, but not fast enough to actually heat up the part. [00:20:08] Bryan: And ultimately over a very long time, in a very painful investigation, it's customer determined that like my fans are cranked in my data center for no reason. We're blowing cold air. And it's like that, this is on the order of like a hundred watts, a server of, of energy that you shouldn't be spending and like that ultimately what that go comes down to this kind of broken software hardware interface at the lowest layer that has real meaningful consequence, uh, in terms of hundreds of kilowatts, um, across a data center. So this stuff has, has very, very, very real consequence and it's such a shadowy world. Part of the reason that, that your listeners that have dealt with this, that our heads will hit the desk is because it is really aggravating to deal with problems with this layer. [00:21:01] Bryan: You, you feel powerless. You don't control or really see the software that's on them. It's generally proprietary. You are relying on your vendor. Your vendor is telling you that like, boy, I don't know. You're the only customer seeing this. I mean, the number of times I have heard that for, and I, I have pledged that we're, we're not gonna say that at oxide because it's such an unaskable thing to say like, you're the only customer saying this. [00:21:25] Bryan: It's like, it feels like, are you blaming me for my problem? Feels like you're blaming me for my problem? Um, and what you begin to realize is that to a degree, these folks are speaking their own truth because the, the folks that are running at real scale at Hyperscale, those folks aren't Dell, HP super micro customers. [00:21:46] Bryan: They're actually, they've done their own thing. So it's like, yeah, Dell's not seeing that problem, um, because they're not running at the same scale. Um, but when you do run, you only have to run at modest scale before these things just become. Overwhelming in terms of the, the headwind that they present to people that wanna deploy infrastructure. The problem is felt with just a few racks [00:22:05] Jeremy: Yeah, so maybe to help people get some perspective at, at what point do you think that people start noticing or start feeling these problems? Because I imagine that if you're just have a few racks or [00:22:22] Bryan: do you have a couple racks or the, or do you wonder or just wondering because No, no, no. I would think, I think anyone who deploys any number of servers, especially now, especially if your experience is only in the cloud, you're gonna be like, what the hell is this? I mean, just again, just to get this thing working at all. [00:22:39] Bryan: It is so it, it's so hairy and so congealed, right? It's not designed. Um, and it, it, it, it's accreted it and it's so obviously accreted that you are, I mean, nobody who is setting up a rack of servers is gonna think to themselves like, yes, this is the right way to go do it. This all makes sense because it's, it's just not, it, I, it feels like the kit, I mean, kit car's almost too generous because it implies that there's like a set of plans to work to in the end. [00:23:08] Bryan: Uh, I mean, it, it, it's a bag of bolts. It's a bunch of parts that you're putting together. And so even at the smallest scales, that stuff is painful. Just architecturally, it's painful at the small scale then, but at least you can get it working. I think the stuff that then becomes debilitating at larger scale are the things that are, are worse than just like, I can't, like this thing is a mess to get working. [00:23:31] Bryan: It's like the, the, the fan issue that, um, where you are now seeing this over, you know, hundreds of machines or thousands of machines. Um, so I, it is painful at more or less all levels of scale. There's, there is no level at which the, the, the pc, which is really what this is, this is a, the, the personal computer architecture from the 1980s and there is really no level of scale where that's the right unit. Running elastic infrastructure is the hardware but also, hypervisor, distributed database, api, etc [00:23:57] Bryan: I mean, where that's the right thing to go deploy, especially if what you are trying to run. Is elastic infrastructure, a cloud. Because the other thing is like we, we've kinda been talking a lot about that hardware layer. Like hardware is, is just the start. Like you actually gotta go put software on that and actually run that as elastic infrastructure. [00:24:16] Bryan: So you need a hypervisor. Yes. But you need a lot more than that. You, you need to actually, you, you need a distributed database, you need web endpoints. You need, you need a CLI, you need all the stuff that you need to actually go run an actual service of compute or networking or storage. I mean, and for, for compute, even for compute, there's a ton of work to be done. [00:24:39] Bryan: And compute is by far, I would say the simplest of the, of the three. When you look at like networks, network services, storage services, there's a whole bunch of stuff that you need to go build in terms of distributed systems to actually offer that as a cloud. So it, I mean, it is painful at more or less every LE level if you are trying to deploy cloud computing on. What's a control plane? [00:25:00] Jeremy: And for someone who doesn't have experience building or working with this type of infrastructure, when you talk about a control plane, what, what does that do in the context of this system? [00:25:16] Bryan: So control plane is the thing that is, that is everything between your API request and that infrastructure actually being acted upon. So you go say, Hey, I, I want a provision, a vm. Okay, great. We've got a whole bunch of things we're gonna provision with that. We're gonna provision a vm, we're gonna get some storage that's gonna go along with that, that's got a network storage service that's gonna come out of, uh, we've got a virtual network that we're gonna either create or attach to. [00:25:39] Bryan: We've got a, a whole bunch of things we need to go do for that. For all of these things, there are metadata components that need, we need to keep track of this thing that, beyond the actual infrastructure that we create. And then we need to go actually, like act on the actual compute elements, the hostos, what have you, the switches, what have you, and actually go. [00:25:56] Bryan: Create these underlying things and then connect them. And there's of course, the challenge of just getting that working is a big challenge. Um, but getting that working robustly, getting that working is, you know, when you go to provision of vm, um, the, all the, the, the steps that need to happen and what happens if one of those steps fails along the way? [00:26:17] Bryan: What happens if, you know, one thing we're very mindful of is these kind of, you get these long tails of like, why, you know, generally our VM provisioning happened within this time, but we get these long tails where it takes much longer. What's going on? What, where in this process are we, are we actually spending time? [00:26:33] Bryan: Uh, and there's a whole lot of complexity that you need to go deal with that. There's a lot of complexity that you need to go deal with this effectively, this workflow that's gonna go create these things and manage them. Um, we use a, a pattern that we call, that are called sagas, actually is a, is a database pattern from the eighties. [00:26:51] Bryan: Uh, Katie McCaffrey is a, is a database reCrcher who, who, uh, I, I think, uh, reintroduce the idea of, of sagas, um, in the last kind of decade. Um, and this is something that we picked up, um, and I've done a lot of really interesting things with, um, to allow for, to this kind of, these workflows to be, to be managed and done so robustly in a way that you can restart them and so on. [00:27:16] Bryan: Uh, and then you guys, you get this whole distributed system that can do all this. That whole distributed system, that itself needs to be reliable and available. So if you, you know, you need to be able to, what happens if you, if you pull a sled or if a sled fails, how does the system deal with that? [00:27:33] Bryan: How does the system deal with getting an another sled added to the system? Like how do you actually grow this distributed system? And then how do you update it? How do you actually go from one version to the next? And all of that has to happen across an air gap where this is gonna run as part of the computer. [00:27:49] Bryan: So there are, it, it is fractally complicated. There, there is a lot of complexity here in, in software, in the software system and all of that. We kind of, we call the control plane. Um, and it, this is the what exists at AWS at GCP, at Azure. When you are hitting an endpoint that's provisioning an EC2 instance for you. [00:28:10] Bryan: There is an AWS control plane that is, is doing all of this and has, uh, some of these similar aspects and certainly some of these similar challenges. Are vSphere / Proxmox / Hyper-V in the same category? [00:28:20] Jeremy: And for people who have run their own servers with something like say VMware or Hyper V or Proxmox, are those in the same category? [00:28:32] Bryan: Yeah, I mean a little bit. I mean, it kind of like vSphere Yes. Via VMware. No. So it's like you, uh, VMware ESX is, is kind of a key building block upon which you can build something that is a more meaningful distributed system. When it's just like a machine that you're provisioning VMs on, it's like, okay, well that's actually, you as the human might be the control plane. [00:28:52] Bryan: Like, that's, that, that's, that's a much easier problem. Um, but when you've got, you know, tens, hundreds, thousands of machines, you need to do it robustly. You need something to coordinate that activity and you know, you need to pick which sled you land on. You need to be able to move these things. You need to be able to update that whole system. [00:29:06] Bryan: That's when you're getting into a control plane. So, you know, some of these things have kind of edged into a control plane, certainly VMware. Um, now Broadcom, um, has delivered something that's kind of cloudish. Um, I think that for folks that are truly born on the cloud, it, it still feels somewhat, uh, like you're going backwards in time when you, when you look at these kind of on-prem offerings. [00:29:29] Bryan: Um, but, but it, it, it's got these aspects to it for sure. Um, and I think that we're, um, some of these other things when you're just looking at KVM or just looks looking at Proxmox you kind of need to, to connect it to other broader things to turn it into something that really looks like manageable infrastructure. [00:29:47] Bryan: And then many of those projects are really, they're either proprietary projects, uh, proprietary products like vSphere, um, or you are really dealing with open source projects that are. Not necessarily aimed at the same level of scale. Um, you know, you look at a, again, Proxmox or, uh, um, you'll get an OpenStack. [00:30:05] Bryan: Um, and you know, OpenStack is just a lot of things, right? I mean, OpenStack has got so many, the OpenStack was kind of a, a free for all, for every infrastructure vendor. Um, and I, you know, there was a time people were like, don't you, aren't you worried about all these companies together that, you know, are coming together for OpenStack? [00:30:24] Bryan: I'm like, haven't you ever worked for like a company? Like, companies don't get along. By the way, it's like having multiple companies work together on a thing that's bad news, not good news. And I think, you know, one of the things that OpenStack has definitely struggled with, kind of with what, actually the, the, there's so many different kind of vendor elements in there that it's, it's very much not a product, it's a project that you're trying to run. [00:30:47] Bryan: But that's, but that very much is in, I mean, that's, that's similar certainly in spirit. [00:30:53] Jeremy: And so I think this is kind of like you're alluding to earlier, the piece that allows you to allocate, compute, storage, manage networking, gives you that experience of I can go to a web console or I can use an API and I can spin up machines, get them all connected. At the end of the day, the control plane. Is allowing you to do that in hopefully a user-friendly way. [00:31:21] Bryan: That's right. Yep. And in the, I mean, in order to do that in a modern way, it's not just like a user-friendly way. You really need to have a CLI and a web UI and an API. Those all need to be drawn from the same kind of single ground truth. Like you don't wanna have any of those be an afterthought for the other. [00:31:39] Bryan: You wanna have the same way of generating all of those different endpoints and, and entries into the system. Building a control plane now has better tools (Rust, CockroachDB) [00:31:46] Jeremy: And if you take your time at Joyent as an example. What kind of tools existed for that versus how much did you have to build in-house for as far as the hypervisor and managing the compute and all that? [00:32:02] Bryan: Yeah, so we built more or less everything in house. I mean, what you have is, um, and I think, you know, over time we've gotten slightly better tools. Um, I think, and, and maybe it's a little bit easier to talk about the, kind of the tools we started at Oxide because we kind of started with a, with a clean sheet of paper at oxide. [00:32:16] Bryan: We wanted to, knew we wanted to go build a control plane, but we were able to kind of go revisit some of the components. So actually, and maybe I'll, I'll talk about some of those changes. So when we, at, For example, at Joyent, when we were building a cloud at Joyent, there wasn't really a good distributed database. [00:32:34] Bryan: Um, so we were using Postgres as our database for metadata and there were a lot of challenges. And Postgres is not a distributed database. It's running. With a primary secondary architecture, and there's a bunch of issues there, many of which we discovered the hard way. Um, when we were coming to oxide, you have much better options to pick from in terms of distributed databases. [00:32:57] Bryan: You know, we, there was a period that now seems maybe potentially brief in hindsight, but of a really high quality open source distributed databases. So there were really some good ones to, to pick from. Um, we, we built on CockroachDB on CRDB. Um, so that was a really important component. That we had at oxide that we didn't have at Joyent. [00:33:19] Bryan: Um, so we were, I wouldn't say we were rolling our own distributed database, we were just using Postgres and uh, and, and dealing with an enormous amount of pain there in terms of the surround. Um, on top of that, and, and, you know, a, a control plane is much more than a database, obviously. Uh, and you've gotta deal with, uh, there's a whole bunch of software that you need to go, right. [00:33:40] Bryan: Um, to be able to, to transform these kind of API requests into something that is reliable infrastructure, right? And there, there's a lot to that. Uh, especially when networking gets in the mix, when storage gets in the mix, uh, there are a whole bunch of like complicated steps that need to be done, um, at Joyent. [00:33:59] Bryan: Um, we, in part because of the history of the company and like, look. This, this just is not gonna sound good, but it just is what it is and I'm just gonna own it. We did it all in Node, um, at Joyent, which I, I, I know it sounds really right now, just sounds like, well, you, you built it with Tinker Toys. You Okay. [00:34:18] Bryan: Uh, did, did you think it was, you built the skyscraper with Tinker Toys? Uh, it's like, well, okay. We actually, we had greater aspirations for the Tinker Toys once upon a time, and it was better than, you know, than Twisted Python and Event Machine from Ruby, and we weren't gonna do it in Java. All right. [00:34:32] Bryan: So, but let's just say that that experiment, uh, that experiment did ultimately end in a predictable fashion. Um, and, uh, we, we decided that maybe Node was not gonna be the best decision long term. Um, Joyent was the company behind node js. Uh, back in the day, Ryan Dahl worked for Joyent. Uh, and then, uh, then we, we, we. [00:34:53] Bryan: Uh, landed that in a foundation in about, uh, what, 2015, something like that. Um, and began to consider our world beyond, uh, beyond Node. Rust at Oxide [00:35:04] Bryan: A big tool that we had in the arsenal when we started Oxide is Rust. Um, and so indeed the name of the company is, is a tip of the hat to the language that we were pretty sure we were gonna be building a lot of stuff in. [00:35:16] Bryan: Namely Rust. And, uh, rust is, uh, has been huge for us, a very important revolution in programming languages. you know, there, there, there have been different people kind of coming in at different times and I kinda came to Rust in what I, I think is like this big kind of second expansion of rust in 2018 when a lot of technologists were think, uh, sick of Node and also sick of Go. [00:35:43] Bryan: And, uh, also sick of C++. And wondering is there gonna be something that gives me the, the, the performance, of that I get outta C. The, the robustness that I can get out of a C program but is is often difficult to achieve. but can I get that with kind of some, some of the velocity of development, although I hate that term, some of the speed of development that you get out of a more interpreted language. [00:36:08] Bryan: Um, and then by the way, can I actually have types, I think types would be a good idea? Uh, and rust obviously hits the sweet spot of all of that. Um, it has been absolutely huge for us. I mean, we knew when we started the company again, oxide, uh, we were gonna be using rust in, in quite a, quite a. Few places, but we weren't doing it by fiat. [00:36:27] Bryan: Um, we wanted to actually make sure we're making the right decision, um, at, at every different, at every layer. Uh, I think what has been surprising is the sheer number of layers at which we use rust in terms of, we've done our own embedded firmware in rust. We've done, um, in, in the host operating system, which is still largely in C, but very big components are in rust. [00:36:47] Bryan: The hypervisor Propolis is all in rust. Uh, and then of course the control plane, that distributed system on that is all in rust. So that was a very important thing that we very much did not need to build ourselves. We were able to really leverage, uh, a terrific community. Um. We were able to use, uh, and we've done this at Joyent as well, but at Oxide, we've used Illumos as a hostos component, which, uh, our variant is called Helios. [00:37:11] Bryan: Um, we've used, uh, bhyve um, as a, as as that kind of internal hypervisor component. we've made use of a bunch of different open source components to build this thing, um, which has been really, really important for us. Uh, and open source components that didn't exist even like five years prior. [00:37:28] Bryan: That's part of why we felt that 2019 was the right time to start the company. And so we started Oxide. The problems building a control plane in Node [00:37:34] Jeremy: You had mentioned that at Joyent, you had tried to build this in, in Node. What were the, what were the, the issues or the, the challenges that you had doing that? [00:37:46] Bryan: Oh boy. Yeah. again, we, I kind of had higher hopes in 2010, I would say. When we, we set on this, um, the, the, the problem that we had just writ large, um. JavaScript is really designed to allow as many people on earth to write a program as possible, which is good. I mean, I, I, that's a, that's a laudable goal. [00:38:09] Bryan: That is the goal ultimately of such as it is of JavaScript. It's actually hard to know what the goal of JavaScript is, unfortunately, because Brendan Ike never actually wrote a book. so that there is not a canonical, you've got kind of Doug Crockford and other people who've written things on JavaScript, but it's hard to know kind of what the original intent of JavaScript is. [00:38:27] Bryan: The name doesn't even express original intent, right? It was called Live Script, and it was kind of renamed to JavaScript during the Java Frenzy of the late nineties. A name that makes no sense. There is no Java in JavaScript. that is kind of, I think, revealing to kind of the, uh, the unprincipled mess that is JavaScript. [00:38:47] Bryan: It, it, it's very pragmatic at some level, um, and allows anyone to, it makes it very easy to write software. The problem is it's much more difficult to write really rigorous software. So, uh, and this is what I should differentiate JavaScript from TypeScript. This is really what TypeScript is trying to solve. [00:39:07] Bryan: TypeScript is like. How can, I think TypeScript is a, is a great step forward because TypeScript is like, how can we bring some rigor to this? Like, yes, it's great that it's easy to write JavaScript, but that's not, we, we don't wanna do that for Absolutely. I mean that, that's not the only problem we solve. [00:39:23] Bryan: We actually wanna be able to write rigorous software and it's actually okay if it's a little harder to write rigorous software that's actually okay if it gets leads to, to more rigorous artifacts. Um, but in JavaScript, I mean, just a concrete example. You know, there's nothing to prevent you from referencing a property that doesn't actually exist in JavaScript. [00:39:43] Bryan: So if you fat finger a property name, you are relying on something to tell you. By the way, I think you've misspelled this because there is no type definition for this thing. And I don't know that you've got one that's spelled correctly, one that's spelled incorrectly, that's often undefined. And then the, when you actually go, you say you've got this typo that is lurking in your what you want to be rigorous software. [00:40:07] Bryan: And if you don't execute that code, like you won't know that's there. And then you do execute that code. And now you've got a, you've got an undefined object. And now that's either gonna be an exception or it can, again, depends on how that's handled. It can be really difficult to determine the origin of that, of, of that error, of that programming. [00:40:26] Bryan: And that is a programmer error. And one of the big challenges that we had with Node is that programmer errors and operational errors, like, you know, I'm out of disk space as an operational error. Those get conflated and it becomes really hard. And in fact, I think the, the language wanted to make it easier to just kind of, uh, drive on in the event of all errors. [00:40:53] Bryan: And it's like, actually not what you wanna do if you're trying to build a reliable, robust system. So we had. No end of issues. [00:41:01] Bryan: We've got a lot of experience developing rigorous systems, um, again coming out of operating systems development and so on. And we want, we brought some of that rigor, if strangely, to JavaScript. So one of the things that we did is we brought a lot of postmortem, diagnos ability and observability to node. [00:41:18] Bryan: And so if, if one of our node processes. Died in production, we would actually get a core dump from that process, a core dump that we could actually meaningfully process. So we did a bunch of kind of wild stuff. I mean, actually wild stuff where we could actually make sense of the JavaScript objects in a binary core dump. JavaScript values ease of getting started over robustness [00:41:41] Bryan: Um, and things that we thought were really important, and this is the, the rest of the world just looks at this being like, what the hell is this? I mean, it's so out of step with it. The problem is that we were trying to bridge two disconnected cultures of one developing really. Rigorous software and really designing it for production, diagnosability and the other, really designing it to software to run in the browser and for anyone to be able to like, you know, kind of liven up a webpage, right? [00:42:10] Bryan: Is kinda the origin of, of live script and then JavaScript. And we were kind of the only ones sitting at the intersection of that. And you begin when you are the only ones sitting at that kind of intersection. You just are, you're, you're kind of fighting a community all the time. And we just realized that we are, there were so many things that the community wanted to do that we felt are like, no, no, this is gonna make software less diagnosable. It's gonna make it less robust. The NodeJS split and why people left [00:42:36] Bryan: And then you realize like, I'm, we're the only voice in the room because we have got, we have got desires for this language that it doesn't have for itself. And this is when you realize you're in a bad relationship with software. It's time to actually move on. And in fact, actually several years after, we'd already kind of broken up with node. [00:42:55] Bryan: Um, and it was like, it was a bit of an acrimonious breakup. there was a, uh, famous slash infamous fork of node called IoJS Um, and this was viewed because people, the community, thought that Joyent was being what was not being an appropriate steward of node js and was, uh, not allowing more things to come into to, to node. [00:43:19] Bryan: And of course, the reason that we of course, felt that we were being a careful steward and we were actively resisting those things that would cut against its fitness for a production system. But it's some way the community saw it and they, and forked, um, and, and I think the, we knew before the fork that's like, this is not working and we need to get this thing out of our hands. Platform is a reflection of values node summit talk [00:43:43] Bryan: And we're are the wrong hands for this? This needs to be in a foundation. Uh, and so we kind of gone through that breakup, uh, and maybe it was two years after that. That, uh, friend of mine who was um, was running the, uh, the node summit was actually, it's unfortunately now passed away. Charles er, um, but Charles' venture capitalist great guy, and Charles was running Node Summit and came to me in 2017. [00:44:07] Bryan: He is like, I really want you to keynote Node Summit. And I'm like, Charles, I'm not gonna do that. I've got nothing nice to say. Like, this is the, the, you don't want, I'm the last person you wanna keynote. He's like, oh, if you have nothing nice to say, you should definitely keynote. You're like, oh God, okay, here we go. [00:44:22] Bryan: He's like, no, I really want you to talk about, like, you should talk about the Joyent breakup with NodeJS. I'm like, oh man. [00:44:29] Bryan: And that led to a talk that I'm really happy that I gave, 'cause it was a very important talk for me personally. Uh, called Platform is a reflection of values and really looking at the values that we had for Node and the values that Node had for itself. And they didn't line up. [00:44:49] Bryan: And the problem is that the values that Node had for itself and the values that we had for Node are all kind of positives, right? Like there's nobody in the node community who's like, I don't want rigor, I hate rigor. It's just that if they had the choose between rigor and making the language approachable. [00:45:09] Bryan: They would choose approachability every single time. They would never choose rigor. And, you know, that was a, that was a big eye-opener. I do, I would say, if you watch this talk. [00:45:20] Bryan: because I knew that there's, like, the audience was gonna be filled with, with people who, had been a part of the fork in 2014, I think was the, the, the, the fork, the IOJS fork. And I knew that there, there were, there were some, you know, some people that were, um, had been there for the fork and. [00:45:41] Bryan: I said a little bit of a trap for the audience. But the, and the trap, I said, you know what, I, I kind of talked about the values that we had and the aspirations we had for Node, the aspirations that Node had for itself and how they were different. [00:45:53] Bryan: And, you know, and I'm like, look in, in, in hindsight, like a fracture was inevitable. And in 2014 there was finally a fracture. And do people know what happened in 2014? And if you, if you, you could listen to that talk, everyone almost says in unison, like IOJS. I'm like, oh right. IOJS. Right. That's actually not what I was thinking of. [00:46:19] Bryan: And I go to the next slide and is a tweet from a guy named TJ Holloway, Chuck, who was the most prolific contributor to Node. And it was his tweet also in 2014 before the fork, before the IOJS fork explaining that he was leaving Node and that he was going to go. And you, if you turn the volume all the way up, you can hear the audience gasp. [00:46:41] Bryan: And it's just delicious because the community had never really come, had never really confronted why TJ left. Um, there. And I went through a couple folks, Felix, bunch of other folks, early Node folks. That were there in 2010, were leaving in 2014, and they were going to go primarily, and they were going to go because they were sick of the same things that we were sick of. [00:47:09] Bryan: They, they, they had hit the same things that we had hit and they were frustrated. I I really do believe this, that platforms do reflect their own values. And when you are making a software decision, you are selecting value. [00:47:26] Bryan: You should select values that align with the values that you have for that software. That is, those are, that's way more important than other things that people look at. I think people look at, for example, quote unquote community size way too frequently, community size is like. Eh, maybe it can be fine. [00:47:44] Bryan: I've been in very large communities, node. I've been in super small open source communities like AUMs and RAs, a bunch of others. there are strengths and weaknesses to both approaches just as like there's a strength to being in a big city versus a small town. Me personally, I'll take the small community more or less every time because the small community is almost always self-selecting based on values and just for the same reason that I like working at small companies or small teams. [00:48:11] Bryan: There's a lot of value to be had in a small community. It's not to say that large communities are valueless, but again, long answer to your question of kind of where did things go south with Joyent and node. They went south because the, the values that we had and the values the community had didn't line up and that was a very educational experience, as you might imagine. [00:48:33] Jeremy: Yeah. And, and given that you mentioned how, because of those values, some people moved from Node to go, and in the end for much of what oxide is building. You ended up using rust. What, what would you say are the, the values of go and and rust, and how did you end up choosing Rust given that. Go's decisions regarding generics, versioning, compilation speed priority [00:48:56] Bryan: Yeah, I mean, well, so the value for, yeah. And so go, I mean, I understand why people move from Node to Go, go to me was kind of a lateral move. Um, there were a bunch of things that I, uh, go was still garbage collected, um, which I didn't like. Um, go also is very strange in terms of there are these kind of like. [00:49:17] Bryan: These autocratic kind of decisions that are very bizarre. Um, there, I mean, generics is kind of a famous one, right? Where go kind of as a point of principle didn't have generics, even though go itself actually the innards of go did have generics. It's just that you a go user weren't allowed to have them. [00:49:35] Bryan: And you know, it's kind of, there was, there was an old cartoon years and years ago about like when a, when a technologist is telling you that something is technically impossible, that actually means I don't feel like it. Uh, and there was a certain degree of like, generics are technically impossible and go, it's like, Hey, actually there are. [00:49:51] Bryan: And so there was, and I just think that the arguments against generics were kind of disingenuous. Um, and indeed, like they ended up adopting generics and then there's like some super weird stuff around like, they're very anti-assertion, which is like, what, how are you? Why are you, how is someone against assertions, it doesn't even make any sense, but it's like, oh, nope. [00:50:10] Bryan: Okay. There's a whole scree on it. Nope, we're against assertions and the, you know, against versioning. There was another thing like, you know, the Rob Pike has kind of famously been like, you should always just run on the way to commit. And you're like, does that, is that, does that make sense? I mean this, we actually built it. [00:50:26] Bryan: And so there are a bunch of things like that. You're just like, okay, this is just exhausting and. I mean, there's some things about Go that are great and, uh, plenty of other things that I just, I'm not a fan of. Um, I think that the, in the end, like Go cares a lot about like compile time. It's super important for Go Right? [00:50:44] Bryan: Is very quick, compile time. I'm like, okay. But that's like compile time is not like, it's not unimportant, it's doesn't have zero importance. But I've got other things that are like lots more important than that. Um, what I really care about is I want a high performing artifact. I wanted garbage collection outta my life. Don't think garbage collection has good trade offs [00:51:00] Bryan: I, I gotta tell you, I, I like garbage collection to me is an embodiment of this like, larger problem of where do you put cognitive load in the software development process. And what garbage collection is saying to me it is right for plenty of other people and the software that they wanna develop. [00:51:21] Bryan: But for me and the software that I wanna develop, infrastructure software, I don't want garbage collection because I can solve the memory allocation problem. I know when I'm like, done with something or not. I mean, it's like I, whether that's in, in C with, I mean it's actually like, it's really not that hard to not leak memory in, in a C base system. [00:51:44] Bryan: And you can. give yourself a lot of tooling that allows you to diagnose where memory leaks are coming from. So it's like that is a solvable problem. There are other challenges with that, but like, when you are developing a really sophisticated system that has garbage collection is using garbage collection. [00:51:59] Bryan: You spend as much time trying to dork with the garbage collector to convince it to collect the thing that you know is garbage. You are like, I've got this thing. I know it's garbage. Now I need to use these like tips and tricks to get the garbage collector. I mean, it's like, it feels like every Java performance issue goes to like minus xx call and use the other garbage collector, whatever one you're using, use a different one and using a different, a different approach. [00:52:23] Bryan: It's like, so you're, you're in this, to me, it's like you're in the worst of all worlds where. the reason that garbage collection is helpful is because the programmer doesn't have to think at all about this problem. But now you're actually dealing with these long pauses in production. [00:52:38] Bryan: You're dealing with all these other issues where actually you need to think a lot about it. And it's kind of, it, it it's witchcraft. It, it, it's this black box that you can't see into. So it's like, what problem have we solved exactly? And I mean, so the fact that go had garbage collection, it's like, eh, no, I, I do not want, like, and then you get all the other like weird fatwahs and you know, everything else. [00:52:57] Bryan: I'm like, no, thank you. Go is a no thank you for me, I, I get it why people like it or use it, but it's, it's just, that was not gonna be it. Choosing Rust [00:53:04] Bryan: I'm like, I want C. but I, there are things I didn't like about C too. I was looking for something that was gonna give me the deterministic kind of artifact that I got outta C. But I wanted library support and C is tough because there's, it's all convention. you know, there's just a bunch of other things that are just thorny. And I remember thinking vividly in 2018, I'm like, well, it's rust or bust. Ownership model, algebraic types, error handling [00:53:28] Bryan: I'm gonna go into rust. And, uh, I hope I like it because if it's not this, it's gonna like, I'm gonna go back to C I'm like literally trying to figure out what the language is for the back half of my career. Um, and when I, you know, did what a lot of people were doing at that time and people have been doing since of, you know, really getting into rust and really learning it, appreciating the difference in the, the model for sure, the ownership model people talk about. [00:53:54] Bryan: That's also obviously very important. It was the error handling that blew me away. And the idea of like algebraic types, I never really had algebraic types. Um, and the ability to, to have. And for error handling is one of these really, uh, you, you really appreciate these things where it's like, how do you deal with a, with a function that can either succeed and return something or it can fail, and the way c deals with that is bad with these kind of sentinels for errors. [00:54:27] Bryan: And, you know, does negative one mean success? Does negative one mean failure? Does zero mean failure? Some C functions, zero means failure. Traditionally in Unix, zero means success. And like, what if you wanna return a file descriptor, you know, it's like, oh. And then it's like, okay, then it'll be like zero through positive N will be a valid result. [00:54:44] Bryan: Negative numbers will be, and like, was it negative one and I said airo, or is it a negative number that did not, I mean, it's like, and that's all convention, right? People do all, all those different things and it's all convention and it's easy to get wrong, easy to have bugs, can't be statically checked and so on. Um, and then what Go says is like, well, you're gonna have like two return values and then you're gonna have to like, just like constantly check all of these all the time. Um, which is also kind of gross. Um, JavaScript is like, Hey, let's toss an exception. If, if we don't like something, if we see an error, we'll, we'll throw an exception. [00:55:15] Bryan: There are a bunch of reasons I don't like that. Um, and you look, you'll get what Rust does, where it's like, no, no, no. We're gonna have these algebra types, which is to say this thing can be a this thing or that thing, but it, but it has to be one of these. And by the way, you don't get to process this thing until you conditionally match on one of these things. [00:55:35] Bryan: You're gonna have to have a, a pattern match on this thing to determine if it's a this or a that, and if it in, in the result type that you, the result is a generic where it's like, it's gonna be either the thing that you wanna return. It's gonna be an okay that contains the thing you wanna return, or it's gonna be an error that contains your error and it forces your code to deal with that. [00:55:57] Bryan: And what that does is it shifts the cognitive load from the person that is operating this thing in production to the, the actual developer that is in development. And I think that that, that to me is like, I, I love that shift. Um, and that shift to me is really important. Um, and that's what I was missing, that that's what Rust gives you. [00:56:23] Bryan: Rust forces you to think about your code as you write it, but as a result, you have an artifact that is much more supportable, much more sustainable, and much faster. Prefer to frontload cognitive load during development instead of at runtime [00:56:34] Jeremy: Yeah, it sounds like you would rather take the time during the development to think about these issues because whether it's garbage collection or it's error handling at runtime when you're trying to solve a problem, then it's much more difficult than having dealt with it to start with. [00:56:57] Bryan: Yeah, absolutely. I, and I just think that like, why also, like if it's software, if it's, again, if it's infrastructure software, I mean the kinda the question that you, you should have when you're writing software is how long is this software gonna live? How many people are gonna use this software? Uh, and if you are writing an operating system, the answer for this thing that you're gonna write, it's gonna live for a long time. [00:57:18] Bryan: Like, if we just look at plenty of aspects of the system that have been around for a, for decades, it's gonna live for a long time and many, many, many people are gonna use it. Why would we not expect people writing that software to have more cognitive load when they're writing it to give us something that's gonna be a better artifact? [00:57:38] Bryan: Now conversely, you're like, Hey, I kind of don't care about this. And like, I don't know, I'm just like, I wanna see if this whole thing works. I've got, I like, I'm just stringing this together. I don't like, no, the software like will be lucky if it survives until tonight, but then like, who cares? Yeah. Yeah. [00:57:52] Bryan: Gar garbage clock. You know, if you're prototyping something, whatever. And this is why you really do get like, you know, different choices, different technology choices, depending on the way that you wanna solve the problem at hand. And for the software that I wanna write, I do like that cognitive load that is upfront. With LLMs maybe you can get the benefit of the robust artifact with less cognitive load [00:58:10] Bryan: Um, and although I think, I think the thing that is really wild that is the twist that I don't think anyone really saw coming is that in a, in an LLM age. That like the cognitive load upfront almost needs an asterisk on it because so much of that can be assisted by an LLM. And now, I mean, I would like to believe, and maybe this is me being optimistic, that the the, in the LLM age, we will see, I mean, rust is a great fit for the LLMH because the LLM itself can get a lot of feedback about whether the software that's written is correct or not. [00:58:44] Bryan: Much more so than you can for other environments. [00:58:48] Jeremy: Yeah, that is a interesting point in that I think when people first started trying out the LLMs to code, it was really good at these maybe looser languages like Python or JavaScript, and initially wasn't so good at something like Rust. But it sounds like as that improves, if. It can write it then because of the rigor or the memory management or the error handling that the language is forcing you to do, it might actually end up being a better choice for people using LLMs. [00:59:27] Bryan: absolutely. I, it, it gives you more certainty in the artifact that you've delivered. I mean, you know a lot about a Rust program that compiles correctly. I mean, th there are certain classes of errors that you don't have, um, that you actually don't know on a C program or a GO program or a, a JavaScript program. [00:59:46] Bryan: I think that's gonna be really important. I think we are on the cusp. Maybe we've already seen it, this kind of great bifurcation in the software that we writ

Originally intended to point out what a Crisis looks like, in the futile hope that maybe people in the USA would recognize when they were making them. Alas, this was not the case, and so we have a real peak Crisis happening.        Can we tell the start of a Fourth Turning by noticing the frequency and intensity of nation-level unforced errors? A look at the Soviet Union during the 1980s, when in retrospect the nation was clearly falling apart, and the unforced errors during that decade that might have been good indicators of what was happening.     https://www.airspacemag.com/history-of-flight/the-notorious-flight-of-mathias-rust-7101888/ "At about this time, Soviet investigators would later tell Rust, radar controllers realized something was terribly wrong, but it was too late for them to act."   In the 1980s, the Reagan administration released a publication called "Soviet Military Power" which was frankly intended to make the Union of Soviet Socialist Republics look more powerful than it was. In 1989, someone FINALLY put out a response to it, called Soviet Military Power, Annotated" which pointed out that it was frankly a propaganda document. Unfortunately, the annotations were also frankly propaganda. At one point it alludes to Rust's flight as having a lot of lucky coincidences that just happened to embarrass the Soviet Union on Border Guard day. It implies, that is, that Mathias Rust's flight sure looked like an intentional propaganda stunt that must have had direct help from someone who wanted to embarrass the USSR> Anyway, if it was the case that this was anything else, I'm rather confident that Rust would have been "disappeared" a while ago.     Googling us intelligence tracking Mathias Rust leads to a "Secrets of Signals Intelligence During the Cold War" - nothing there, really, that I used here, but it was interesting reading. (Okay, it no longer seems to lead there, but you can search for it directly, and there are some links that are evidently to the book itself.) https://en.wikipedia.org/wiki/Fall_of_the_Berlin_Wall https://en.wikipedia.org/wiki/History_of_Solidarity https://en.wikipedia.org/wiki/Polish_Round_Table_Agreement   https://en.wikipedia.org/wiki/Severomorsk_Disaster https://www.nytimes.com/1984/07/11/world/soviet-naval-blast-called-crippling.html   Listing them here for additional clarity and impact.   1979 - Afghanistan 1980 - Solidarity 1983 - KAL 007 1985 - Chernenko dies 1986 - Chernobyl 1987 - Mathias Rust 1989 - Berlin Wall Falls 1991 - August Coup   HBO's miniseries on Chernobyl influenced my views of the Chernobyl disaster by making the causes clear enough to be enthralling cinema. It's a good intro to the disaster, although parts of it are fictionalized. I could not find the cosmonaut cartoon, but saw it at work every day in 1985-1987. There was another cartoon I remember but also couldn't find about Solidarity: Polish &  Soviet leaders discuss the labor union, and assume that it was engineered by reactionary forces in the West. It then shows a small group of people reading from The Communist Manifest: Workers of the world, Unite! You have nothing to lose but your chains! That sixth Star Trek film is The Undiscovered Country, released in December 1991, only a few weeks before the official dissolution of the Soviet Union. https://www.imdb.com/title/tt0102975/

Bryan Cantrill, the co-founder and CTO of Oxide Computer company, speaks with host Jeremy Jung about challenges in deploying hardware on-premises at scale. They discuss the difficulty of building up Samsung data centers with off-the-shelf hardware, how vendors silently replace components that cause performance problems, and why AWS and Google build their own hardware. Bryan describes the security vulnerabilities and poor practices built into many baseboard management controllers, the purpose of a control plane, and his experiences building one in NodeJS while struggling with the runtime's future during his time at Joyent. He explains why Oxide chose to use Rust for its control plane and the OpenSolaris-based Illumos as the operating system for their vertically integrated rack-scale hardware, which is designed to help address a number of these key challenges. Brought to you by IEEE Computer Society and IEEE Software magazine.

Originally aired 02/22/2026This week host @Jackgreenstalk (aka @Jack_Greenstalk on X/instagram backup account) [or contact via email: JackGreenstalk47@gmail.com] is joined by panel with , @spartangrown on instagram or X f.k.a. Twitter at https://x.com/grown43626 or email spartangrown@gmail.com for contacting spartan outside social media, any alternate profiles on other social medias using spartan's name, and photos are not actually spartan grown be aware, @NoahtheeGrowa on instagram and @TheAmericanOne on youtube aka @theamericanone_with_achenes on instagram who's amy aces can be found at amyaces.com on instagram, and Rust Brandon of @fulcrop.sciences / fulcrop.ceo regained @Rust.Brandon instagram page, and products can be found at bokashiearthworks.com .... This week we missed Matthew Gates aka @SynchAngel on instagram and twitter @Zenthanol on youtube who offers IPM direct chat for $1 a month on patreon.com/zenthanol , @drmjcoco from cocoforcannabis.com as well as youtube where he tests and reviews grow lights and has grow tutorials and @drmjcoco on instagram and @ATG Acres Aaron The Grower aka @atgacres his products can be found at atgacres.com view his instagram to find out details about drops!

In this episode of SaaS Fuel, Jeff Mains sits down with Marc Rust, founder of Consequently Creative, to challenge everything you think you know about branding. Marc reveals why the strongest brands aren't built on logos and taglines—they're built on relationships, courtship, and genuine human connection.You'll discover why "different is always better," how visual storytelling requires education and courtship, and why the interview process should focus on hunger, not resumes. Marc delivers a master class in putting people first, technology last, and building brands that create emotional resonance in an increasingly automated world.Key Takeaways[4:30] - Branding as the operating system for transformation and growth—not a nice-to-have, but the foundation for how companies evolve[5:55] - The AI capability trap: Technology is being sold based on what it can do, not what humans actually need it to do[7:17] - Why the Segway failed: Lack of tangible examples and use cases people could identify with (spoiler: only mall cops use them)[10:40] - The POST method framework: People → Objectives → Strategy → Technology (not technology first)[11:53] - Courtship in branding: Building relationships requires pacing—don't propose on the first date[14:07] - The John Hancock disaster: $60-per-click ads driving traffic to pages that didn't sell what customers wanted[19:30] - Don't make it about you: Focus on your audience's needs, not your own features and capabilities[25:45] - Hiring for hunger: Job interviews should reveal passion and drive, not rehash the resume[29:00] - The playground philosophy: Good playgrounds challenge kids and create healthy fear—easy things don't build character[31:00] - Education as courtship: Walking people through design choices (like using red) builds appreciation and buy-in[34:15] - Brand color recognition: How cell phone carriers own colors so deeply you know exactly who "the blue one" is[35:30] - The Marlboro Formula One story: When cigarette ads were banned, they just showed "red and white racing car"—the brand connection was already there[40:00] - The clarity checklist: What do you do? Who is it for? Why does it matter? What makes you different? What happens next?Tweetable Quotes"Branding is not a nice-to-have—it's the operating system for transformation and growth." — Marc Rust"AI needs to be viewed as a tool first and foremost, not sold based on capability." — Marc Rust"Don't make it about you. It's about your audience. We live in a 'me, me, me' era—so if you focus on them, you'll have engagement." — Marc Rust"Trust comes only from value. Value + value + value = trust eventually." — Marc Rust"The interview is not a time to go over the resume. Find out if people are hungry." — Marc Rust"A good playground is challenging, has risk in it, and makes kids a little scared. Easy things in life don't bring you anywhere." — Marc Rust (via playground CEO)"Different is always better. Different people are interesting. Same people are boring." — Marc RustSaaS Leadership Lessons1. Start with People, Not Technology (The POST Method)Stop leading with what your technology can do and start with what your people need it to do. Follow the POST framework: People (audience

On episode 32 of Open Source Ready, Brian Douglas and John McBride sit down with Glauber Costa to explore Turso, a Rust-based rewrite of SQLite built for the AI era. They discuss database reliability, open source licensing, and why embedded databases are becoming critical infrastructure for modern agents and applications. The conversation also dives into AI-assisted development and the future of software engineering.

Mark is joined by Bryan Rust of the Pittsburgh Penguins

Mark talks about Crosby missing a month for the Penguins. Bryan Rust joins the show to talk about the Penguins without Sid and his season so far.

Mark is joined by Bryan Rust of the Pittsburgh Penguins See omnystudio.com/listener for privacy information.

Mark talks about Crosby missing a month for the Penguins. Bryan Rust joins the show to talk about the Penguins without Sid and his season so far. See omnystudio.com/listener for privacy information.

Welcome to the Personal Development Trailblazers Podcast! In today's episode, we're talking about how to create healthy boundaries so you can build a peaceful, balanced life.Scott Rust is a CHT, NLP Practitioner, Success and Life Coach, PK, GM, Speaker, and Best-Selling Author. He has always had a passion for teaching and storytelling, which is what took him to both China and Spain as a TEFL educator. Scott now runs SCOTTICVS, his personal brand and business, where he helps people with "whatever is grinding their gears" as "the Mental Mechanic," since he has a lot of different tools to take care of whatever needs fixing for folks that day.Connect with Scott Here: https://www.facebook.com/Scotticvs/https://www.linkedin.com/in/scotticvs/www.scotticvs.com/homeGrab the freebie here: https://scotticvs.com/mp3_gift_buildupyourself===================================If you enjoyed this episode, remember to hit the like button and subscribe. Then share this episode with your friends.Thanks for watching the Personal Development Trailblazers Podcast. This podcast is part of the Digital Trailblazer family of podcasts. To learn more about Digital Trailblazer and what we do to help entrepreneurs, go to DigitalTrailblazer.com.Are you a coach, consultant, expert, or online course creator? Then we'd love to invite you to our FREE Facebook Group where you can learn the best strategies to land more high-ticket clients and customers. QUICK LINKS: APPLY TO BE FEATURED: https://app.digitaltrailblazer.com/podcast-guest-applicationDIGITAL TRAILBLAZER: https://digitaltrailblazer.com/

Jedd McFatter interview is gonna rock you to the bone

Some artifacts don't belong. Buried in sand. Hidden in shipwrecks. Locked in museum cases. Objects that shouldn't exist — at least not according to the official timeline. In this episode, we dive into the world of Out-of-Place Artifacts — the Baghdad Battery, the Antikythera Mechanism, the Iron Pillar of Delhi, the Sabu Disc, the Nimrud Lens, the Wedge of Aiud — relics that feel like glitches in history itself. Ancient batteries. Mechanical computers 2,000 years ahead of their time. Rust-proof iron. Precision stonework that modern tools struggle to replicate. Are these just misunderstood relics… Or evidence that something has been forgotten — or erased? Was there lost technology? A vanished civilization? Cycles of collapse we refuse to acknowledge? The deeper you look, the stranger it gets. History tells a story. But sometimes the artifacts tell a different one. Listen. Learn. Laugh. Question everything. Support the show & join The Skult: Patreon.com/SofaKingPodcast Merch & SK Gear: SofaKingPodcast.com More Episodes: / @sofakingpodcast Sofakingpodcast.com Produced by Brad Taylor Music by Brad Taylor Full songs available on Patreon Intro "Enter the Sofa King Chamber" End Song "Out Of Place" Artwork by Brent Vantassel #AncientMysteries#LostCivilizations#AncientTechnology#HiddenHistory#OOPART#OutOfPlaceArtifacts#AntikytheraMechanism#BaghdadBattery#Unexplained#HistoryDocumentary#ForbiddenHistory#TimelineGlitch

Welcome back to the monthly design diaries series of 2026 where I am holding myself accountable toward putting out more games.   We're back to talk more Gardens of Rust, the post-catastrophe survival and community rebuilding game by myself and Christian from the DMs After Dark.    In episode 2 I walk through the Character Creation process and create two different characters to try and show the breadth of characters you may be going into this game with!   Hopefully this gets you excited and thinking about the types of characters you'd want to bring to the post-collapse world who can rebuild a community and new life in the Rust. Definitely join the DMs After Dark Discord or email me to tell me about a character idea, we can build it together!   ----more---- Join the DMs After Dark Discord channel!   I made a Ko-Fi if you feel absurdly generous and want to help cover podcast hosting costs & all the upkeep. I'm still working on whether I want to offer anything special over there or just give my extreme gratitude (maybe some stickers or something in the mail) to those who donate, but no pressure whatsoever :)   Where to Follow Rene Plays Games: LinkTree |  BlueSky | Threads | Instagram | Facebook | DMs After Dark Rene's Games: MECH | MECH Cities 2 | One Last Quest | I Know I Know You, But I Don't Know How... email: RenePlaysGamesPod@gmail.com   Music in the Episode (in order of appearance): Rene Plays Games Theme written & produced by Dan Pomfret | @danfrombothbands

This is a recap of the top 10 posts on Hacker News on February 23, 2026. This podcast was generated by wondercraft.ai (00:30): The Age Verification Trap: Verifying age undermines everyone's data protectionOriginal post: https://news.ycombinator.com/item?id=47122715&utm_source=wondercraft_ai(01:55): Ladybird adopts Rust, with help from AIOriginal post: https://news.ycombinator.com/item?id=47120899&utm_source=wondercraft_ai(03:21): Americans are destroying Flock surveillance camerasOriginal post: https://news.ycombinator.com/item?id=47127081&utm_source=wondercraft_ai(04:47): Elsevier shuts down its finance journal citation cartelOriginal post: https://news.ycombinator.com/item?id=47119530&utm_source=wondercraft_ai(06:12): Pope tells priests to use their brains, not AI, to write homiliesOriginal post: https://news.ycombinator.com/item?id=47119210&utm_source=wondercraft_ai(07:38): Binance fired employees who found $1.7B in crypto was sent to IranOriginal post: https://news.ycombinator.com/item?id=47127396&utm_source=wondercraft_ai(09:04): Hetzner (European hosting provider) to increase prices by up to 38%Original post: https://news.ycombinator.com/item?id=47121029&utm_source=wondercraft_ai(10:29): Magical Mushroom – Europe's first industrial-scale mycelium packaging producerOriginal post: https://news.ycombinator.com/item?id=47119274&utm_source=wondercraft_ai(11:55): FreeBSD doesn't have Wi-Fi driver for my old MacBook, so AI built one for meOriginal post: https://news.ycombinator.com/item?id=47129361&utm_source=wondercraft_ai(13:21): ASML unveils EUV light source advance that could yield 50% more chips by 2030Original post: https://news.ycombinator.com/item?id=47125349&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

It seems like every year there's a new disease infecting our crops here in Wisconsin and most recently for corn we've been seeing an increase in southern rust. Ashley Madson, a technical agronomist with Bayer, is here to share a bit of the history of this disease within Wisconsin and some tips for the 2026 season on choosing the right seed and best input management.See omnystudio.com/listener for privacy information.

Wes McKinney on the mythical agent-month, install Peon Ping to employ a Peon today, Andreas Kling explains why Ladybird is adopting Rust, Cloudflare has a new MCP server that's quite efficient, and Elliot Bonneville thinks the only moat left is money.

Wes McKinney on the mythical agent-month, install Peon Ping to employ a Peon today, Andreas Kling explains why Ladybird is adopting Rust, Cloudflare has a new MCP server that's quite efficient, and Elliot Bonneville thinks the only moat left is money.

Wes McKinney on the mythical agent-month, install Peon Ping to employ a Peon today, Andreas Kling explains why Ladybird is adopting Rust, Cloudflare has a new MCP server that's quite efficient, and Elliot Bonneville thinks the only moat left is money.

¿Es Python siempre la mejor opción para tus scripts de automatización? En este episodio, Lorenzo profundiza en una de las discusiones más recurrentes de la comunidad: la estabilidad de los scripts frente a la comodidad de los módulos de terceros. Acompaña a nuestro experto en Linux mientras desglosa los motivos que lo llevaron a abandonar soluciones basadas en Python para la gestión de metadatos de audio.Descubre ID3CLI, una herramienta potente y ligera escrita en Rust que soluciona los problemas de retrocompatibilidad y fallos en tiempo de ejecución. Aprenderás cómo automatizar el etiquetado de tus podcasts extrayendo datos directamente de archivos Markdown, eliminando la necesidad de introducir información manualmente en herramientas gráficas. Analizamos la importancia de tener binarios compilados que simplemente "funcionan", permitiéndote centrarte en crear contenido en lugar de arreglar herramientas rotas.Temas destacados del episodio: Bash vs Python: ¿Cuándo el "follón" de compilar merece la pena? Los peligros de depender de módulos de terceros que cambian sin previo aviso. De EasyTag a la automatización total en la terminal. Uso de Front Matter y RipGrep para un flujo de trabajo eficiente. Soporte de metadatos para Apple y carátulas en múltiples formatos. Capítulos,00:00:00 Introducción: El dilema de Bash vs Python00:00:48 El riesgo de las dependencias de terceros en Python00:01:35 La obsesión por la automatización de metadatos00:03:01 Flujo de trabajo: De EasyTag a la Terminal00:05:36 Extrayendo datos del Front Matter en Markdown00:07:24 Herramientas antiguas: ID3 y MiD3v2 (Mutagen)00:09:12 El colapso de los módulos y la necesidad de compilar00:10:13 Presentando ID3CLI: La solución definitiva en Rust00:11:53 Características técnicas y soporte de formatos (MP3, OGG, FLAC)00:13:48 Integración de ID3CLI en scripts de automatización00:15:23 Reflexión sobre la importancia de los metadatos00:16:42 Nuevo proyecto: El podcast "La Era de las Distros"00:17:47 Comunidad y cierre del episodioAdemás, Lorenzo nos habla sobre su nuevo podcast "La Era de las Distros", una mirada necesaria a las distribuciones Linux que marcaron un hito en la informática española como LinEx o Guadalex. ¡Disfruta del episodio y optimiza tu entorno Linux!Más información y enlaces en las notas del episodio

In this episode we talk with Ken Lemoine who also is the executive Director of the BayState Motor Festival the 2026 show will be on Father's Day https://www.waxoyl-usa.com/https://baystatemotorfestival.com/

Ironside's claw.With Gourley And Rust bonus content on PATREON and merchandise on REDBUBBLE.With Gourley and Rust theme song by Matt's band, TOWNLAND.And also check out Paul's band, DON'T STOP OR WE'LL DIE. Hosted on Acast. See acast.com/privacy for more information.

I have a theory that only bad projects get finished — good ones keep finding new things to do. Asciinema is a case in point. What started as a way to share terminal sessions with friends has, over 14 years, grown into a full suite of tools covering recording, hosting, playback, and live streaming — and been rebuilt multiple times along the way. So what does it actually take to record and replay a terminal session faithfully in a browser?Joining us for this conversation is Marcin Kulik, Asciinema's creator. The project's architecture has passed through almost every interesting corner of software engineering: a Python recorder built around pseudo-terminals (PTY), a ClojureScript terminal emulator for the browser that hit performance limits with immutable data structures and garbage collection pressure, a move to Rust compiled to WebAssembly, a Go experiment that didn't last, and a new Rust CLI for concurrent live streaming backed by an Elixir/Phoenix server that calls Rust code via NIFs. The same Rust terminal emulator library now powers all three components — the browser player, the server, and the CLI.If you've ever looked at those terminal animations embedded in a README and wondered what's underneath them, or if you're interested in how a passionate open-source developer navigates 14 years of language changes and rewrites, this conversation has plenty to offer.---Support Developer Voices on Patreon: https://patreon.com/DeveloperVoicesSupport Developer Voices on YouTube: https://www.youtube.com/@DeveloperVoices/joinAsciinema: https://asciinema.orgAsciinema Docs: https://docs.asciinema.orgAsciinema CLI (GitHub): https://github.com/asciinema/asciinemaAsciinema Player (GitHub): https://github.com/asciinema/asciinema-playerAsciinema Server (GitHub): https://github.com/asciinema/asciinema-serverAVT - Rust terminal emulator library: https://github.com/asciinema/avtvt-clj - the original ClojureScript terminal emulator: https://github.com/asciinema/vt-cljPaul Williams' ANSI/VT100 State Machine Parser: https://vt100.net/emu/dec_ansi_parserRust: https://www.rust-lang.orgWebAssembly: https://webassembly.orgSolidJS: https://www.solidjs.comElixir: https://elixir-lang.orgPhoenix Framework: https://www.phoenixframework.orgRustler (Rust NIFs for Elixir/Erlang): https://github.com/rusterlium/rustlerClojure: https://clojure.orgClojureScript: https://clojurescript.orgcmatrix: https://github.com/abishekvashok/cmatrixMarcin Kulik on GitHub: https://github.com/ku1ikMarcin Kulik on Mastodon: https://hachyderm.io/@ku1ikMarcin Kulik on asciinema.org: https://asciinema.org/~ku1ik"They're Made Out of Meat" demo: https://asciinema.org/a/746358Kris on Bluesky: https://bsky.app/profile/krisajenkins.bsky.socialKris on Mastodon: http://mastodon.social/@krisajenkinsKris on LinkedIn: https://www.linkedin.com/in/krisjenkins/---0:00 Intro2:28 What Is Asciinema?4:48 How Asciinema Started9:51 The Problem of Parsing Terminal Output14:07 Building a Cross-Platform Recorder17:01 Rewriting the Parser in ClojureScript22:19 The Hidden Complexity of Terminals29:28 Rendering Terminals in the Browser39:47 When ClojureScript Can't Keep Up45:28 Moving to Rust and WebAssembly52:01 The Go Experiment57:43 Adding Live Terminal Streaming1:07:12 Can You Scrub Back in a Live Stream?1:14:40 Editing Recordings1:25:27 Outro

Does brain science need a new grand plan? Is the brain less like an assembly line and more like a weather system? What does this mean for what counts as explanatory, and how might AI help us in the near future? What does any of this have to do with how the drug Ritalin got its name? Today we’ll speak with neuroscientist Nicole Rust, author of Elusive Cures.

The Linux Kernel 6.19 is out, the Rust experiment is over, and it's time to talk about 7.0. Vim 9.2 is out, with a bit of a weird new feature in its changelogs, and IPFire is an intriguing, community-driven security domain block list. PearOS has a new release for those seeking an Apple-inspired Linux experience, and Linux Mint is adjusting its release schedule to better manage developer and tester schedules. River is a new project trying to do Wayland support with a modular Desktop stack, and Mesa 26.0 is out with impressive performance gains. For tips, we have cull for finding and deleting big files, a systemd program for detecting if the OS is running virtualized, preload for caching applications in ram, and new_script for a script-writing tool that *doesn't* feature an LLM. You can find the show notes at https://bit.ly/3ZCNcEc and happy Linux'ing! Host: Jonathan Bennett Co-Hosts: Rob Campbell, Ken McDonald, and Jeff Massie Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

https://www.linkedin.com/in/brian-ogrady/ - my linkedin https://www.linkedin.com/company/qdrant/ - company linkedin https://qdrant.tech/contact-us - contact us https://github.com/qdrant/qdrant/ - Qdrant GH https://github.com/qdrant/qdrant-edge-demo - Qdrant Edge running on smart glasses Mike on LinkedIn Coder Radio on Discord Mike's Oryx Review Alice Alice Jumpstart Offer Vorpal Mike in USA Today