Podcasts about Nix

Bucky Irving is practicing; AJB looks INCREDIBLE; Nix; Mahomes

In hour one, Dover and Cecil start the show by looking at the Stanley Cup Final! What did we see from the Carolina Hurricanes, and what can the Avs learn from them? A big trade suggestion was made, but how do we feel about it? What does Champ Bailey think about Bo Nix? What can keep Nix from being a top 10 QB? How serious is this ankle injury? Can Jaylen Waddle help the Broncos get into the top half of the NFL in explosive plays?

In hour three, Dover and Cecil look at the Stanley Cup Final! What did we see from the Carolina Hurricanes, and what can the Avs learn from them? What does Champ Bailey think about Bo Nix? What can keep Nix from being a top 10 QB? How serious is this ankle injury? Can Jaylen Waddle help the Broncos get into the top half of the NFL in explosive plays? We react to the biggest story in college football and how teams are reacting to the news.

On a Monday edition of Hot Takes, Eric Goodman and Troy Renck discuss the Broncos going through another week of OTAs. Who needs Nix to have a great season more: Sean Payton, Davis Webb or Nix himself? A chat about the MLB Hall of Fame and steroid use. Connor McDavid won the Ted Lindsay Award for the fifth time, given to the Most Outstanding Player. Why didn't Nathan MacKinnon finish in the Top-3? And what does this say about how other players view MacKinnon? The guys finish the podcast by getting into the Avs shakeup in the front office, with GM Chris MacFarland going to Nashville. Tune in to another episode of Hot Takes with Eric Goodman and Troy Renck! Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Daniel Buitrago & Brandon Fifield are back in studio with return guests Josh Nix and his lovely bride Mrs. Nix to find out all about Crazy J's!   The AWP studio live edge table by Knik River Customs, episode #4 w/Josh Nix in March of 2021, spring moose attacks in Anchor Town, Hilleberg Tent event brought to you by Barney's Sport Chalet & Alaska Wild Project coming up on Monday June 22nd, “This Day in Alaska History” brought to you by “Northern Waste”, 1840: The British flag replaced the Russian flag over Fort Dionysius in Southeast Alaska. The Hudson's Bay Company subsequently renamed the outpost Fort Stikine, 1924: The U.S. Congress passed the Indian Citizenship Act, granting American citizenship to all Native Americans born within the U.S. This had a profound impact on Alaska Native populations, extending their voting rights while recognizing their sovereign tribal affiliations, 1974: KISS performed at the Sundowner Drive-In Theater in Anchorage. Because of the Alaskan summer sun, the show started around 11:00 PM but still took place under a bright blue sky. The band built a stage directly in front of the drive-in's massive movie screen, digging the first guide boat out the trees, starting Crazy J's, vandalism at the boat launch, “PINKY” the bonker, 4AM starts to late night hook-ups, from the Knik to the Kenai, getting respect from your guide competition, separating from the pack through connections, full circle to the drift track in Montana, Kid friendly Northern Pike, Trivia Brought to our buy Connoisseur Crude          Visit our website - www.alaskawildproject.com Follow us on Instagram - www.instagram.com/alaskawildproject Watch on YouTube - www.youtube.com/@alaskawildproject $upport on Patreon - www.patreon.com/alaskawildproject Visit Crazy J's Guiding - www.crazyjsguiding.com

Wir sprechen über aktuelle Technikthemen rund um Infrastruktur, Open Source und KI. Ein Schwerpunkt ist Sebastians stark automatisierte Kubernetes-Umgebung auf Talos Linux mit GitOps und KI-Agenten unter menschlicher Kontrolle. Außerdem diskutieren wir Plattformfragen, Sicherheits- und Lieferkettenthemen sowie verschiedene KI-Entwicklungen. Zum Schluss greifen wir noch einige kleinere Themen aus dem Entwickleralltag und Werkzeuge für lokale LLMs auf. Blast from the Past Kubernetes Cluster ist nun live! https://www.siderolabs.com/talos-linux https://github.com/kreativmonkey/homelab-gitops payphonetag Froscon Toter der Woche Aus für De-Mail – warum das @ das eingekringelte e besiegte wero Aus für Ubuntu Pastebin – Abschaltung Ende Juni 2026 feedburner Untoter der Woche Stuxnet's Older Brother Revealed After 21 Years (video) fast16 | Mystery Shadow Brokers Reference Reveals High-Precision Software Sabotage 5 Years Before Stuxnet AI der Woche Continue Y/N Torvalds nennt KI Bug Reports “reine Zeitverschwendung” … aber curl Entwickler “zeigt sich versöhnlich” https://hothardware.com/news/new-ai-cyber-worm-thinks-up-its-own-attacks-to-infect-computers Anthropic: Weltweite Pause bei KI-Entwicklung ‘sinnvoll’ Anthropic Bewertung 965 Millarden rsync drama rsync analyse Google Chrome silently installs a 4 GB AI model on your device EU AI Act: Transparenzpflichten ab August 2026 Jakob gewinnt Gemma4 12B Bonsai 4b News Backblaze has quietly stopped backing up your data Debian must ship reproducible packages Cloudflare kauft Vite: Open Source und herstellerneutral – mit Millionenfonds https://arstechnica.com/security/2026/06/dozens-of-red-hat-packages-backdoored-through-its-offical-npm-channel/ https://www.golem.de/news/nur-ein-client-noetig-http-2-bomb-legt-webserver-in-sekunden-lahm-2606-209396.html Blog Post Themen Was eigentlich wenn kein GitHub? Ghostty Is Leaving GitHub Codeberg Gitlab BitBucket (nein!) Hackergarten 3D-Druck der Woche Bambu Lab: I’m reposting your code & I dare you to sue me. (video) Bambu Lab 3D printers: Never again (video) baltobu Zauberstab zum Bezahlen Weltumwelttag “PET Recycling” Mimimi der Woche modules C++20 tooling Python click Nix & SELinux Nix: cross-compiling Updates sind scheiße! Brother Drucker mit neuem Zertifikat Cosmic Desktop Nix Logo Lesefoo I put a datacenter GPU into my PC searchcode.com's SQLite database is probably 6 terabytes bigger than yours How I run multiple $10K MRR companies on a $20/month tech stack Serving a Website on a Raspberry Pi Zero Running Entirely in RAM NixOS auf Flint 2 You don’t love systemd timers enough! Picks IPv8 is finaly here Internet Protocol Version 8 (IPv8) The Unsolved Mystery of Lorem Ipsum (video) ODROID H5 Mechanical Pencil Umweltkosten durch Vibe Coding: Tool berechnet CO₂-Ausstoß für Claude Code Artikel von Heise taken (again)

In hour three, Dover and Cecil react to the news of the day. Chris McFarland has left the Avalanche to join Nashville. What does this mean for the Avs moving forward? Coach Bednar's job appears to be safe. Will Joe Sakic start his search for a new general manager? The Broncos have OTAs this week. What stories are we looking out for? How serious is Nix’s ankle injury, and could it be completely overblown?

In hour one, Dover and Cecil start the show by welcoming back Cecil from his weekend trip! The Broncos have OTAs this week. What stories are we looking out for? How serious is Nix’s ankle injury, and could it be completely overblown? What does an NFL team need to be a championship roster? Do the Broncos have those pieces? Who are the most overrated and underrated Broncos as we enter OTAs? We look at all the trades that went down yesterday in the NFL.   

For the second hour of Stokely and Evans with Mark Schlereth, Stink tells us about the snake he encountered when he was doing work around the house. They speculate what’s going on with Jared Bednar’s job amid all the radio silence. Could an extension be on the way? The guys get Stink’s educated opinion on the national media’s beef with Bo Nix and he projects where Bo will rank among his peers in the next few years. What’s Trending? The Nuggets want to make a deal, open season on OKC, and the Rockies’ game of the year happened over the weekend.

https://rhr.tv/stream Sentiment Analysis https://x.com/sullymichaelvan/status/2059646236966137982 Fidelity Glitch https://x.com/adi_baradwaj/status/2059422632215548143 NY legal complaint seeks title to 39,069 allegedly abandoned bitcoin wallets https://static1.squarespace.com/static/694884477ae7ad3f7b78981b/t/6a038dcea3e5b83386bf21a4/1778617806647/2026-05-01+%5B21%5D-%5B22%5D+Summons+%26+Amended+Complaint.pdf Is it Shkreli? https://x.com/MartinShkreli/status/2059711308921028692 Former CIA officer accused of stealing $40M in gold bars and foreign currency https://www.cnn.com/2026/05/28/politics/former-cia-officer-public-money-theft Texas app store age-verification law allowed to take effect for now https://www.texastribune.org/2026/05/28/texas-apple-google-app-store-age-verification/ South Carolina social media law criticized as statewide age surveillance https://reclaimthenet.org/south-carolina-social-media-surveillance-law Walz signs Minnesota bill adding social media protections for children https://minnesotareformer.com/briefs/walz-signs-bill-enacting-social-media-guardrails-for-minnesota-children/ Developer Spotlight: Kurt Unger https://opensats.org/blog/developer-spotlight-kurt-unger CFTC Approves Kalshi Perpetual BTC Future https://www.cftc.gov/PressRoom/PressReleases/9240-26 North Korea | Dictatorship Implements Rice Price Controls North Korea's authoritarian regime is attempting to cap rice prices after a sharp food price surge, but the policy is making the shortage worse. According to Daily NK, the regime ordered local officials to stop street vendors from selling rice above a state-imposed ceiling. This action was in response to rice prices rising above 30,000 North Korean won ($33.33) per kilogram. Officials and undercover agents are now inspecting markets, checking sellers' account books, and confiscating rice from those accused of charging too much. Traders are responding by pulling rice from public stalls and selling it privately from homes or other hidden locations. For North Koreans, the state's actions make rice harder to find and more expensive. FinancialFreedomReport.org Matching Hashes: Reproducing the Guix-built Bitcoin Core release binary with Nix https://b10c.me/projects/027-bitcoind-gunix-match/ ngit-cli v2.5.0 adds PR defaults, GRASP fallback handling, and checkout fixes https://github.com/DanConwayDev/ngit-cli/releases/tag/v2.5.0 Europa VPN Market https://europa.westernbtc.com/ Google employee charged with insider trading https://www.justice.gov/usao-sdny/pr/google-employee-charged-insider-trading Data broker location data used to target and kill U.S. troops https://www.techdirt.com/2026/05/28/enemies-are-exploiting-unregulated-data-broker-location-data-to-target-and-kill-u-s-troops/ 3:33 - Opening riff 9:03 - Dashboard 16:48 - Angry plebs 37:48 - Fidelity glitch 42:48 - Abandoned wallets 48:53 - Texas age verification 56:33 - Drone warfare 1:04:48 - OpenSats dev spotlight 1:06:18 - CFTC Kalshi 1:10:48 - HRF Story of the Week 1:13:18 - Matching Hashes 1:15:23 - Zaps & Boosts 1:22:03 - Software updates 1:26:16 - Google insider trading 1:29:08 - Data brokers risk troops 1:33:03 - US constitution on the blockchain Shoutout to our sponsors: Coinkite https://coinkite.com/ Strike https://strike.me/ Stakwork https://stakwork.ai/ Salt of the Earth https://drinksote.com/rhr Follow Marty Bent: Twitter https://twitter.com/martybent Nostr https://primal.net/marty Newsletter https://tftc.io/martys-bent/ Podcast https://tftc.io/podcasts/ Follow Odell: Nostr https://primal.net/odell Newsletter https://discreetlog.com/ Podcast https://citadeldispatch.com/

For the second hour of Stokely and Evans with Mark Schlereth, they pick which day they would take off if they had a 4-day work week. They debate whether Jared Bednar’s job is safe after he survived yesterday. Von Miller continues to lobby for a return to Denver but the guys explain why it isn’t the right time. They tell everybody to smash the over on Bo Nix’s TD’s this season. What’s Trending? Bednar’s job security, Cale’s shoulder, and Mike Vrabel mastering the art of deflection.  

In hour 2 of The Drive, Zach and Phil react to Chris Simms' rankings of the top 32 quarterbacks in the NFL. Where did Bo Nix land on the rankings? We go quarterback by quarterback and debate if Nix should be ahead or behind those individuals. Could Bo Nix be a top 10 quarterback after this season? We hear from Simms on why ranking Nix was so difficult with the limited sample size of two NFL seasons. Does Bo need to work on being more efficient and consistent? How much running will we see from Nix in year 3? Today's "Three Count" includes an all-time upset in tennis earlier today at the French Open, Shohei Ohtani doing Shohei Ohtani things by hitting a homerun and pitching 6 innings of no-hit ball last night, and previewing the Colorado and CSU announced game times and networks. We react to Von Miller making another plea to be a member of the Broncos again. Do the Broncos have a roster spot to use on Miller while they are in a championship window? 

In hour 4 of The Drive, Zach and Phil react to Chris Simms' rankings of the top 32 quarterbacks in the NFL. Where did Bo Nix land on the rankings? We go quarterback by quarterback and debate if Nix should be ahead or behind those individuals. We hear from Simms on Nix's clutch gene and the tools he possesses. Does Bo need to work on being more efficient and consistent? Is Bo's age a concern as he will end next season as a 27-year-old? We react to Von Miller making another plea to be a member of the Broncos again. Do the Broncos have a roster spot to use on Miller while they are in a championship window? We wrap up the show with DenverSports.com's Aniello Piro joining the show to discuss Jared Bednar's job security with the Avalanche. 

On episode 38 of Open Source Ready, Brian Douglas and John McBride speak with Graham Christensen, CEO of Determinate Systems, about the evolution of the Nix ecosystem and why more organizations are embracing reproducible infrastructure. They discuss secure package management, enterprise adoption challenges, open source business models, and how AI tooling is rapidly reshaping software engineering workflows.

Dat gifft je Spreekwöörd, de tatsächli wohr sünd, de good sünd, üm de Würklichkeit to beschrieven. Spreekwöörd, de den „Nogel op'n Kopp“ dreept. „Steter Dropen höhlt den Steen“, to'n Bispeel. Dor gifft dat nix an to tippen. Dat is so. Un dat kann man in veele ünnerscheedliche Situatschoon‘ as Metapher insetten. Dat gifft overs ook Spreekwöörd, bi de ick ni so seeker bün, dat man dor wat mit anfang‘ kann. Nehmt wi mol „Nomen est Omen“. Dat is Latein un dat heet: „De Noom is 'n Vörteeken.“ Jo, wat is dat denn för'n Orakelie? Na jo, wi nutzt dat je in 'n annern Sinn. Mehr so: „De Noom is Programm“, also de Noom seggt ut, wokeen oder wat man is oder so. Tscha, dat geiht tomeist overs fix no achtern los. Dat is astrein‘ Bleudsinn. Ick heff to'n Bispeel noch keen droopen, de Schmidt heet un de sick mit Hommer un Amboss utkinnt. Mach ween, wat dat een gifft, overs ick kinn keeneen. Ook keen Meier, de würkli 'n Meier is, oder 'n Müller, de weet, wo man anstänniged Mehl mokt. Ick kinn keen Wagner, de 'n Kutschrad buun kann un keen Tischler, de tatsächli Discher is. Un wenn ick bi mi kiek: Heiko Kroll? Fangt wi mol mit Heiko an. Dat is de fries'sche Form vun Heinrich, un dat bedüüd „mächtiger Herr över't Land“. Hmm. Bün ick ni. Dat bedüüd overs ook „Herrscher in't Huus“. Ha, dor froog man mol mien Madam no, wat ick to Huus to seggen heff. Nix! Kannst vergeeten. Un Kroll? Dat heet so veel as gelockted Hoor. Wat? De poor Fusseln, de ick noch op'n Kopp heff gifft ni mol 'n richtige Frisuur af un Locken al dreemol ni. Haut ni hen. Dor froog ick mi, mit wat för Omens dat erst Lüüd as „Heidemarie Wieczorek-Zeul“ vun de SPD to kriegen hebbt! Man weet dat ni. Man mutt ook keen slechten Minsch ween, wenn man ut „Ekel“ in NRW kümmt. Un wenn man ut „Oberbillig“ in Nordrhein-Westfooln kümmt, heet dat noch lang ni, dat man nix wert is. Tscha, wenn't no mi gung, schull dat Spreekwoord „Nomen ‚non‘ est Omen“ heeten, also De Noom hett överhaupt nix to bedüüden. Un zack, hett man weller wat, an dat man sick gor ni argern mutt… In düssen Sinn

Ryota Sawada is software engineer at Numtide and the release lead of Kubernetes 1.36 code name Haru. He has over a decade of experience mainly in the finance industry including working on Cloud Native technologies, and outside of Cloud Native, he's been tinkering with Emacs and Nix.   Do you have something cool to share? Some questions? Let us know: - web: kubernetespodcast.com - mail: kubernetespodcast@google.com - twitter: @kubernetespod - bluesky: @kubernetespodcast.com   News of the week Etcd version 3.7.0 is out Merge Forward Community Truepositive Links from the interview Kubernetes 1.35 codename Haru Release theme and logo Logo designer User Namespaces Workload API Workload Aware Scheduling (WAS) DRA features graduating to Stable GKE 10 years and SIG Networking, With Antonio Ojea  

For the second hour of Stokely and Evans with Mark Schlereth, Mike Rice and Marcello Romano sit in for the guys for this Memorial Day. The guys try to diagnose the biggest problem with the Avs that has led them to an 0-3 hole. Mike and Cello point out the Avs’ issues across the roster and on the bench and rank which one takes highest priority. They project what Bo Nix and the offense will look like under the leadership of Davis Webb. What’s Trending? The Avs are trending down, Spurs making believers, the closest Indy 500 ever, and the untimely passing of Kyle Busch.  

Jan, Daniel und Mario wundern sich: Hungerattacken? Fehlanzeige. Buffende Teenager? Nix. Anstrengende Boomer? Schon eher. Für wen und warum und wieso dieser Film, entzieht sich unserem Verständnis.

Take the 2026 AI Engineering Survey and get >$2k in credits and AIE WF tickets!This was recorded before Railway suffered a major GCP outage on May 19, despite being a multi-AZ, multi-zone mesh ring, with HA fiber interconnects between their Metal GCP AWS, because workload discoverability was unintentionally still tied to GCP. All has been resolved with a post-mortem.Railway did not start as an AI infrastructure company.It was founded in 2020 years before agents became the default way people thought about deploying software. Jake Cooper, formerly at Bloomberg and Uber, started Railway with a simple obsession: the activation energy to ship something to production should be near zero. Push code, get a URL, iterate. No Docker files, no Kubernetes manifests, no Ansible scripts stacked on Ansible scripts.For years, this was a slow grind. Railway spent its first 18 months hand-acquiring its first 100 users with Jake personally greeting every Discord signup on a second monitor.Today, Railway has raised $124m and is growing very fast. A 35-person team supports 3 million users, adding roughly 100,000 signups a week. Their bare metal data centers have a 3-month payback period vs. renting in the cloud, with 70% margins funding aggressive cloud bursting when needed. The servers they own have actually appreciated in value as RAM prices have climbed basically meaning the value of their hardware now exceeds the capital they've raised.From rebuilding Railway's network overlay over a weekend to moving the vast majority of workloads onto its own bare metal data centers, Jake Cooper is trying to build a new cloud for an agent-native world. In this episode, Railway's founder and “conductor” joins swyx and Alessio to unpack why the next era of software infrastructure is not just “Heroku but newer,” what agents need that humans did not, and why the old deployment loop of Git, PRs, CI/CD, and static cloud resources may be heading for a rewrite.We go deep on Railway's infrastructure stack: own-metal data centers, three-month cloud payback periods, cloud bursting, data center debt, Railpack, Nixpacks, Temporal, feature flags, Central Station, content-addressable filesystems, agent-safe production forks, and why the CLI may become more important than the canvas in an agent world. Jake also shares the founder journey behind Railway, how the company survived losing $500K/month, why it now serves millions of users with only 35 people, and why he believes the pull request is dying.We discuss:* How Railway went from a slow six-year grind to adding 100,000 users a week* How Railway thinks about agents as the next dominant software species* Why agents need version control, observability, compute, storage, and orchestration at 1000x scale* The economics of Railway's own-metal data centers and three-month payback* How Railway uses cloud bursting while scaling its own infrastructure* Why data center debt can be a better tool than venture debt for infra startups* Central Station, Railway's internal system for clustering customer feedback and incidents* Why responsible disclosure and over-communication matter for platforms* Why feature flags, progressive rollouts, and shadow traffic are essential for agents* Temporal's strengths, pain points, and why workflows matter for agents* Railpack, Nixpacks, Nix, and lazy-loaded content-addressable filesystems* Why “cattle, not pets” may change if you can clone the pets* Why Railway is building a new cloud from scratch instead of copying hyperscalers* The solo founder path, focus, writing, and how Jake thinks about company buildingRailway:* Website: https://railway.com/* X: https://x.com/RailwayJake Cooper:* LinkedIn: https://www.linkedin.com/in/thejakecooper/* X: https://x.com/JustJakeTimestamps00:00:00 Introduction: What Is Railway?00:02:07 Jake's Path to Railway00:06:13 Railway's Six-Year Growth Story00:08:52 Rebuilding the Business After the Free Tier00:11:17 Agents as the Next Software Platform00:13:29 Railway's Infrastructure Philosophy00:15:42 Bare Metal, Cloud Economics, and the Compute Crunch00:17:22 Cloud Bursting and Five-Cloud Networking00:20:20 Data Center Debt and Infra Financing00:23:31 Data Centers in Space00:25:24 What Agents Need From Infrastructure00:28:24 CLIs, Canvas, and Agent-Native UX00:35:15 Central Station, Incidents, and Responsible Disclosure00:40:30 Safe Rollouts, SRE Agents, and Production Forks00:45:00 AI SRE, Specs, Code, and Tests00:48:24 Self-Replicating Infrastructure and the New Serverless00:53:18 Heroku, Temporal, and Workflow Engines01:04:07 Railpack, Nixpacks, and Lazy-Loaded Filesystems01:06:01 Coding Agents, Token Spend, and Roadmap Acceleration01:10:56 The Pull Request Is Dying01:12:28 Feature Flags and the Agent-Era SDLC01:16:15 Cattle, Pets, and Cloning Machines01:19:29 Solo Founder Lessons01:24:12 Focus, GPUs, and Building a New Cloud01:28:20 Closing ThoughtsTranscriptAlessio [00:00:00]: Hey, everyone. Welcome to the Latent Space Podcast. This is Alessio, founder of Kernel Labs, and I'm joined by Swyx, editor of Latent Space.Swyx [00:00:10]: Hey, hey, hey. Today we're in the studio with Jake Cooper of Railway.Alessio [00:00:14]: Conductor of Railway.Swyx [00:00:15]: Conductor at Railway. Yeah.Alessio [00:00:16]: Choo-choo.Swyx [00:00:17]: Do you actually have that anywhere, like on your business card?Jake [00:00:20]: We call some of our volunteer moderators conductors. I don't have a business card. We're not that big yet. At some point I will. I got handed a nice business card from the Supermicro folks, and I was like, “Damn, this is pretty official.”Swyx [00:00:30]: Business cards are coming back.Jake [00:00:32]: They're cool. They're hip. The conductor thing is good. We're trying to figure out what we want to call each other internally. Some people think it's super cringe and say, “You don't need a name for people internally.” Some people want to call each other something. We still don't have a really good one.Jake [00:00:55]: We've got New Railcrews, Trainiacs. Nothing has stuck yet.Swyx [00:01:00]: I like Trainiac. Trainiac sounds good. Railwayians. For those who don't know, what is Railway? Let's give people a crisp definition up front.Jake [00:01:09]: Railway is the easiest way to ship anything. You go to the canvas, or you talk with Claude, and you say, “Deploy a Postgres instance, deploy my GitHub repository, run this code,” and you're off to the races.Swyx [00:01:22]: You've got a nice animation on the landing page.Jake [00:01:24]: Thank you. None of my work, by the way. They don't let me touch the design stuff anymore.Jake [00:01:25]: We want to make it trivially easy not just to deploy things, but to evolve applications over time. Most tooling right now stacks entropy on top of entropy: Docker, Kubernetes, Ansible scripts, and all these other things. If we can version all of your software and keep track of all the changes, then we can make it trivial to clone environments, fork into a parallel universe, get copies of production data, get copies of any services, make changes, validate them, and collapse them back in without reproducing everything across a staging environment.The Railway Origin Story: From Uber Systems to a New CloudSwyx [00:02:07]: I was looking at your background: Bloomberg, Uber. Nothing immediately stands out as, “This guy is going to found the next great platform as a service.” What prepared you for Railway?Jake [00:02:21]: It was curiosity to keep going deeper. I started out on front-end stuff, working on Wolfram Mathematica and porting it over. Then I briefly moved to Bloomberg, then toward Uber and distributed systems, taking the Jump Bikes systems and moving them to a distributed system built on top of Cadence, the pre-Temporal Temporal.Swyx [00:02:44]: Which, by the way, I'm happy to talk about, pros and cons.Jake [00:02:48]: Totally.Swyx [00:02:51]: But let's do the Railway story.Jake [00:02:52]: It has been a continual step of wanting an experience. Whether it's walking up to a bike, unlocking it, and having it work frictionlessly, or something else, the depth required to make that happen follows from the experience. A lot of the work I do, and a lot of the team does, is in service of that experience. We fundamentally don't care how deep we have to go. We will swim to the bottom of the swimming pool to get the experience.Jake [00:03:17]: I don't have a physics PhD. I did an EECS degree. It has always been about figuring out the next step: how do we get there? That's what led to starting Railway for that experience and then moving all the way to bare metal data centers. I was adding patches to the kernel this week to get the experience there because I can see how much better it can be.Swyx [00:03:49]: Other patches to the Linux kernel this week?Jake [00:03:51]: Yeah. Not upstream. Our fork.Swyx [00:03:52]: That's a flex. Railpack? No, this is different. This is the OS on top of Railpack?Jake [00:03:57]: No, this is an actual kernel patch. It's always literally: what do we have to do to get that experience? Then figure it out. Anything is figureoutable.Swyx [00:04:10]: Would you send the patch upstream, or does it not fit other use cases?Jake [00:04:13]: Maybe. We have to work out the experience internally. It has to do with the storage layer we're building for some of the agentic stuff. Maybe it'll be useful upstream, but it's deeply useful for us internally.Open Source, Forks, and Non-Deterministic VersioningSwyx [00:04:29]: You mentioned open source before. How do you think about starting from open source, and then coding agents letting you do a lot more from forks of it?Jake [00:04:38]: GitHub's original sin is that it's almost a series of broken pointers. You have this thing, then you clone it, and now you've lost the whole upstream. How do we make it trivial for people to modify really small pieces of it?Jake [00:04:51]: We think of Git in a discrete sense: I've either made a change and merged upstream, or I haven't. What would it look like if it were percentage-based, a little more non-deterministic, or a stream of changes that users traverse as a percentage rolled out in general and then rolled all the way up?Jake [00:05:13]: We have the open-source kickback program and let you deploy templates because we want to make it trivial for people to version these shards over time. It solves a large problem around authentication, authorization, and security. NPM has a way to define, “Don't take any new packages.” The ideal end state is that you roll out progressively to users with the minimum impact zone and continue rolling up. JPMorgan should probably be the last one on the patch line, for all our sakes, because our money and livelihoods are there.Jake [00:05:53]: It's okay if Johnny Vibe Coder gets a broken patch because there's so much entropy in the system that the rubber has to meet the road at some point. You have to test at varying levels.The Long Grind: First Users, Free Tier, and Making the Business WorkSwyx [00:06:13]: I wanted to pull up this glorious chart, which is your usage or number of daily signups?Jake [00:06:22]: Daily signups, I think.Swyx [00:06:24]: You started six years ago. It was a slow grind, and now you're on a rocket ship. You say, “Don't doubt your fight and don't quit.” Maybe pick out certain points that were key inflections for the company.Jake [00:06:40]: At the start, it's about getting your first 100 users, hell or high water. We had a website and a support link. The support link was the Discord channel. I had notifications on with two monitors: the monitor I was working on and the other monitor with Discord. If anybody came in, I was immediately like, “Hey, how's it going?” It was rare, so getting those first 100 users to come back was the start.Jake [00:07:14]: Then you build a consultancy factory because users want all these things. You have to go back to the board and ask, “What is the actual product offering I want to build on top of this?”Jake [00:07:28]: VCs want charts that always go up and to the right, but in reality you don't necessarily want charts that look like that. For us, there have been periods of expansion where we add features to test use cases, and periods of compaction where we ask, “If the experience we have is good, how do we make it significantly better?” Maybe we strip out features that don't fit our ICP anymore.Jake [00:07:57]: The boom from 2022 to 2023 came from the free tier. Everybody under the sun was using it.Swyx [00:08:09]: A lot of Reddit bots and Discord bots.Jake [00:08:12]: And crypto miners. When you build an open product on the internet where anybody can sign up, the internet is a horrible place with so many things. You go through periods of asking, “How do I reach as many people as possible?” Then, “How do I fit the exact use case for the people who really matter and are really excited about this specific thing?”Jake [00:08:39]: Then there was a two-year period of making the actual business work. During the free-tier era, we were losing about half a million dollars a month.Swyx [00:08:59]: On a $20 million bank account.Jake [00:09:02]: On a $20 million bank account with maybe $50,000 a month in revenue. That's a horrible business. I don't know how anybody invested. But you have to go through it and say, “We have an experience people love, but the business has to work.”Jake [00:09:17]: There are two schools of thought. You can run the horrible business all the way up with bad margins, or you can go back and make it work. We've always wanted a super lean team. We're 35 people right now. It's very small.Swyx [00:09:36]: Supporting three million already?Jake [00:09:38]: Yeah. We're adding 100,000 users a week right now, so it's growing fast. We don't want to add headcount for the sake of headcount or throw bodies at problems. We want to build systems. It's hard to build systems during expansion because you're adding things to the system because people are asking for them or things are breaking.Jake [00:10:00]: We had to cut off the free users for a little while, rebuild the business, and make sure it worked. We want to reach as many people as possible because software is important. It's become difficult to create things in the physical world, so it's important to make it easy for people to build in the virtual world and have access to creation. But there are legs to that journey.Jake [00:10:30]: You can see divots in the charts. If you follow between 2025 and 2026, it's either summer or winter. People go on holiday with family.Swyx [00:10:50]: It affects that much?Jake [00:10:51]: Yeah. It's kind of B2C and kind of B2B. People are shipping constantly, then they stop. Our activation curve now shows more people activating on weekdays because we have more business users, so it smooths out over time.Agents as the New Interface to DeploymentSwyx [00:11:17]: Was there a point where you started prioritizing AI development or agent development?Jake [00:11:24]: We've prioritized agentic as a top-of-funnel thing. Over the last six months, we've deeply prioritized agentic as a mechanism to build and deploy things because we believe the curve is so steep and that is how people will build and deploy software.Jake [00:11:42]: It almost fundamentally doesn't matter whether this is dot-com or not because we're all on the internet anyway. If agents are going to deploy a bunch of things and we hit an inference wall at some point, we'll fix those problems. The dominant species over the next 10 years is that we've moved from assembly to C to C++ to JavaScript to words. You're going to need to close that loop.Swyx [00:12:13]: When you say this is dot-com, did you mean buying the domain, or the general case?Jake [00:12:17]: I mean the dot-com era, when companies had a huge run-up because people understood the internet was important. Then they hit bottlenecks, fundamental laws of physics, math didn't work, and everybody came back down to earth. But it didn't matter because the internet became so impactful. If you operate on a long enough time horizon, you should build these things anyway because you can see where it's going.Jake [00:12:45]: That's where I think a lot of agent stuff is. You get to a point where you're running thousands of agents in parallel. What is the inference cost? What is the compute cost? How do you make that efficient? How do you coordinate all this? We have issues coordinating humans; we don't even have good tooling for that. Now we have to figure out how to get agents to coordinate, safely version changes, and know when to raise their hand for someone to intervene. Otherwise it becomes an interrupt factory.Railway's Infrastructure Thesis: Network, Compute, Storage, and MetalSwyx [00:13:19]: Let's go right into the technical side. What are the core infrastructure or architectural beliefs of Railway that allow you to do what you do?Jake [00:13:29]: The primitives matter a lot for us. We need network, compute, storage, and orchestration around it. You need control over a lot of those things. We've talked a lot about how we don't really use Kubernetes because we want higher-order control to place workloads in very specific places.Jake [00:13:48]: The reason is that you have to be very efficient with agents: memory reuse and all these other things, or you're going to massively blow up your cost structure. Being able to rack and stack your own servers and build your own metal unlocks performance and cost. Experiences where you're running 1,000 agents in parallel are not massively cost prohibitive.Jake [00:14:13]: Token use and compute use are blowing up. Over time, those things have to get a lot more efficient. You can get a lot of margin to make those experiences solid by building your own metal. That's all in service of offering a differentiated experience to as many people as humanly possible.Swyx [00:14:51]: You have a data center in Singapore.Jake [00:14:53]: Yeah. We have two in every other region now. In Singapore, we're adding a second one in Q3.Swyx [00:14:58]: What's it like? I've never built a data center. Do you go to Equinix and say, “I want some slots?”Jake [00:15:05]: Yeah. Equinix. You basically go and say, “I want power and I want a cage.” They say, “Great, here's what it's going to be.” You rent the cage for a period of time, fill it with racks and servers, and hook up internet to it. That's all the pieces.Swyx [00:15:36]: Then you handle everything else.Jake [00:15:37]: You handle everything else.Swyx [00:15:39]: What's the math versus clouds doing it for you?Jake [00:15:43]: If we rented in the cloud, our payback period when we go to metal is about three months.Swyx [00:15:50]: Which is crazy.Jake [00:15:51]: It's nuts. That's four years of depreciated hardware. You're going to see a lot of this compute crunch because hyperscalers are buying up a lot of stuff. We're working directly with OEMs, resellers, and people building these machines: Supermicro, Dell, and others.Jake [00:16:11]: Upstream, there's a bunch of supply pressure. When we raised our last round, between deploying capital for servers and now, the amount of money we've raised is less than the amount of money we have in the bank plus the value of the servers because the servers have appreciated as RAM has gone up. It's nuts how valuable hardware has become.Jake [00:16:50]: If you look at hyperscalers, they deployed around $80 billion of capital expenditures this year, and next year will be more. That's a massive infrastructure build-out. You look at that and think it's crazy that they're spending way more than the Manhattan Project. But if every person is going to run dozens or hundreds of agents in parallel, you have no conceptual idea how much compute is required to make that experience happen, even if you're deeply efficient and sharing resources. And that doesn't even count inference.Swyx [00:17:22]: How do you plan the build-out? The growth chart is so vertical. Are you usually at 100% utilization as soon as racks are live? How far ahead are you planning?Jake [00:17:33]: We still maintain cloud presence for bursting. We work with AWS, GCP, and a few other clouds. We can rent, and then the moment we get space or power, we compact those workloads off the cloud. We started on the clouds, then built a system to migrate to our own metal. There's nothing that says you can't continually do that again, and that's exactly what we do. We never want to be compute constrained.Jake [00:18:09]: At the start of the year, we actually became compute constrained because one upstream provider wasn't able to give us quota at the rate we needed, and the hardware was slower. I spent a weekend rebuilding our entire network overlay so we could straddle five clouds: Oracle, AWS, ourselves, GCP, and one other one. We can do more than that now.Jake [00:18:38]: We got into a spot where we were trying to pack instances tight because we couldn't get enough compute. That led to a few reliability issues, which are now past us. I made a tweet pointing out that it's becoming harder and harder to acquire compute at the rate these models need to acquire compute. We got bit by it.Swyx [00:19:15]: How do you think about pricing knowing you might not have your own metal available at all times? Are you pricing assuming you need extra margin if you end up going into the cloud?Jake [00:19:26]: Because we've built out our metal data centers, our margins on metal are around 70%. We can deeply subsidize the cloud business if we want to scale at a reasonable rate. We have a few levers: metal, which makes the margins; cloud burst; debt to buy servers; and venture capital. It's an interesting operational problem: how much cash do we have, how much should we raise, how quickly can we deploy it, and can we scale revenue as quickly as we scale compute?Jake [00:20:05]: If we continue making it trivially easy for people to build and deploy, then the faster we close that loop and the more operationally excellent we are with capital, the faster the business can scale. It's almost a straight linear deployment rate.Financing Infrastructure: Hardware Debt, VC, and Operational LeverageSwyx [00:20:20]: I think infra startups raising debt is a tool people don't utilize enough or know enough about. What can you tell us about that? Is it secured against your CPUs?Jake [00:20:32]: It's secured against our hardware.Swyx [00:20:37]: What rates do you get? Who are the lenders?Jake [00:20:39]: We pay prime plus a spread, and we can refinance any of the debt as rates go down. The terms are pretty good. The unfortunate thing is that Twitter has no nuance, so people say, “Venture debt bad.” But as with all things, there are specific tools and areas where you can be deliberate instead of using one tool as a hammer. Venture capital is not the hammer for everything. You have to explore and figure out what works.Swyx [00:21:12]: VC is usually the most expensive financing you can get.Jake [00:21:15]: Yeah. I also think people think about VC incorrectly from a capital-raising perspective. Most people think, “How do I raise as much money as possible from whoever is probably the best I can get at that time?” That's close to right, but what we've tried to do is figure out what unfair advantage we can buy with that equity.Jake [00:21:34]: It's the most expensive equity you're going to give away at that point in time, assuming the company keeps getting better. How do you use it to work with someone stellar who complements you? In the seed stage, I had never started a company. Ray Tonsing had good advice, and I could text him all the time. He was really fast. Awesome.Jake [00:22:01]: Then with John and Erica at Unusual, they said, “You roughly know what you're doing building a product. We'll mostly leave you alone and be available for advice.” Amazing. Then we got to Series A and the business was an operational tire fire because we didn't know how to scale a business. Work with Erica, and Jordan is over at Redpoint, so bonus.Jake [00:22:28]: Now we've raised from TQ and FPV as we're moving into enterprises. Every step of the way, we've asked: who can we partner with at this specific time to unlock the next section of the journey? I don't know enterprise sales. As an engineer, I can eyeball what features we might need, and we have wonderful people internally who can help. But you want boardroom dynamics where everyone is aligned and asking, “How do we win this?” instead of bickering about strategy.Data Centers in Space and the Physics of ComputeSwyx [00:23:31]: You had a tweet about data centers in space. Why no data centers in space?Jake [00:23:37]: It's not “no data centers in space.” My hot take is that I think it is solvable. I've just never seen anybody solve it.Swyx [00:23:49]: You said, “How are you going to dissipate that much heat in a vacuum?” You're making a physics claim.Jake [00:23:55]: I haven't seen anybody prove how you're going to dissipate that much heat in a vacuum. It doesn't mean it's not possible. It just means nobody has brought it up yet.Swyx [00:24:05]: Astrophage.Jake [00:24:06]: I don't know what that is.Swyx [00:24:07]: The Martian thing. Okay, you're very logical.Jake [00:24:09]: It could work. A lot of people are putting the cart before the horse. They say, “We're going to put data centers in space.” Okay, but how? “We have time to figure it out.” It's like in The Martian where they ask how they're going to intercept something and say, “We'll figure it out.”Swyx [00:24:36]: Making a bet on human invention is weird because you blind trust that it can be solved. But with physics, there are first-principles bounds you can put on it. Maybe not. Maybe you're asking to travel time or break a fundamental thermodynamic law.Jake [00:24:57]: I don't know how VCs do this either. How do you know what's not possible and a grift versus what's possible but sounds completely insane? “We're going to put data centers in space.” Coin flip as to which it is, and I guess you'll know in 10 years. That's one cycle.What Agents Need: Versioning, Observability, and 1,000x ScaleSwyx [00:25:23]: Moving back to agents. The branching, fast spin-up, and orchestration you do feels like pre-work that happened to be exactly what agents want. What do agents want differently than humans?Jake [00:25:37]: They want the ability to version things. It's not that different; it materializes slightly differently. Agents want a way to test changes incrementally. Engineers have feature flags. Is there a reason agents can't use feature flags? I don't think so.Jake [00:25:54]: They want version control. Can we use Git or not Git? That one is up in the air. I think something outside Git will emerge for how we version these things over time. They need observability. You need to query what happened, when it happened, which steps failed, traces, logs, metrics, and all the rest. They need network, compute, and storage. They need to write files, save files, iterate on files, and snapshot file systems.Jake [00:26:25]: A lot of what humans needed is in line with what agents need. Branching and forking are not different; we're just moving 1,000 times quicker. It can look like you need something massively different, but what you need is something massively better than what existed. You need orchestration massively better than Kubernetes. You need networking probably better than Envoy. It goes all the way down the stack.Jake [00:26:55]: If the workload profile doesn't change so much as it gets massively compressed because you need thousands of these things, what assumptions change? etcd is going to melt. You need to replace it with something. You can go all the way down the stack and say, “That part has to change, that part has to change, and that part has to change.”Jake [00:27:19]: The interesting thing about the super-exponential curve is that you have to build systems where you can rip out those parts at any time because a new bottleneck might emerge. You get good at parallel agents, and a different part of the system breaks. So it's similar to what humans needed, but at 1,000x scale.Jake [00:27:55]: How do you do code review in the age of agents?Swyx [00:28:00]: You throw more agents at it.Jake [00:28:01]: You don't. But then who reviews for CVEs and all these other things?Swyx [00:28:07]: More agents.Jake [00:28:08]: And that's how we hit the inference wall. You can continually throw agents at the problem, but I think there's a limit to the number of agents you can throw at a problem.CLI, Agent Handles, and Closing the LoopSwyx [00:28:24]: You already had a CLI before it was cool. How is the shape of what you're exposing changing, if at all?Jake [00:28:28]: CLIs have always been cool. The CLI changes because we think about how to give Claude, Codex, ChatGPT, or any model a handhold.Jake [00:28:50]: A CLI is a single command: deploy, get logs, and so on. Things that were prohibitively annoying to humans are not annoying to agents. They're nice. If I handed you a CLI with 40 arguments and 600 flags, you'd think, “I'm never going to use all of this.” But if you hand it to an agent, it says, “This is excellent. I have so many handles to work with.”Jake [00:29:24]: If you're going to expose things to agents that way, you want as many handles as possible where they can get information, query dynamic information, and close the loop quickly. Most problems right now are about how to close the loop as quickly as possible. Where does the agent get stuck, and how can you remove that?Jake [00:29:49]: Telemetry is important. If you can tell where the agent gets stuck from the CLI and say, “12% of people deviate from the happy path because of this, and now I add this argument and drive it down to 2%,” you massively increase the rate of loop closure.Jake [00:30:03]: That's how we think about not just the CLI, but every point in the dashboard. It's a user journey: I hear about Railway. I get something deployed. I get my first green build or aha moment. I see an endpoint, logs, whatever. Then I iterate. The iteration loop is indefinite. The user wants to deploy a new thing, a Postgres instance, change code, and keep iterating.Jake [00:30:36]: If you focus on the iteration loops and what's blocking them from closing quickly, one thing we say internally is: you never want to be waiting on compute anymore. You always want to be waiting on intelligence. If you're waiting on compute, there's a bottleneck that needs to be destroyed because eventually that bottleneck becomes so large that another workflow emerges to change it.Jake [00:31:04]: We've built a product where you push code, build it, and so on. But I fundamentally believe the push-pull loop is going away. We'll get to a point where you make a small change in production, that change is versioned across your infrastructure, you're working alongside copy-on-write versions of your database and infrastructure, and then you merge it in and it's instantaneously live. That's the holy grail of loops. The push-pull-rebuild thing is a point of friction that we're removing entirely.Canvas as Output: Dashboards, Context Anchors, and HyperstructuresSwyx [00:31:43]: It's incredibly fast. If anyone hasn't tried it, that fast feedback is great. My hot take is that Railway was famous for its canvas, which visualizes your infrastructure and lets you manipulate it visually. But that was for humans. For the next phase of growth, Railway CLI is more important than canvas.Jake [00:32:05]: The canvas is funny because it's a mechanism to show changes over time. You're right that previously we used it a lot as an input. Moving forward, its goal is more like an output. You would go to the canvas, make changes, see them, and watch your infrastructure evolve. Now agents have access to the CLI and can make those changes. So the canvas becomes an output: what information does the human need at this moment to make suitable decisions about control requests? Do I approve this or not?Jake [00:32:57]: It also has to be an anchor for your context, a port in the storm. Think of it like layers in a file system. You start with a project, then drill down into services, then into a function or code, because you want to represent the entire thing not just in your head, but in the canvas. Other people can share that representation, think on the same wavelength, and move quickly.Jake [00:33:33]: A lot of organizations get in trouble as they scale because all the context lives in someone's head. “How does this microservice work?” “I have no idea; go ask this person.” Then you have whole categories of products built around context discovery. A lot of that melts away if you have a solid hierarchy and can infinitely nest services, code, context, and everything else all the way down. That's what lets you build these structures over time.Jake [00:34:18]: It's also what lets us build what I've called hyperstructures: things that are way bigger. You look at the Golden Gate Bridge and ask, “How did we build that?” There's a meme that we lost the technology. To some extent, yes, because the coordination that built those things evolved and changed. We lost some of the art of building structure as we jammed everything into Slack.Swyx [00:34:52]: But you jam everything in Discord.Jake [00:34:53]: Same point. It doesn't matter. It's message passing and interrupts, message passing and interrupts.Swyx [00:35:00]: So you're arguing there should be something better and more structured than Slack?Jake [00:35:04]: Yeah. For sure. I think Slack is awful, and Discord is awful too.Central Station: Context Routing, Support, and Incident ClustersSwyx [00:35:09]: This is the equivalent of my mom test. What have you done that has your solution to this?Jake [00:35:15]: Internally, we've built a tool called Central Station that aggregates all the context from our users. Every piece of feedback, every customer support item, everything gets aggregated into clusters. If an incident is brewing, we can determine how many users are affected and break off a discussion based on that.Jake [00:35:40]: That is more helpful than long-running channels where you're trying to decide which channel to put something in. If you can dynamically aggregate information and dynamically route it to the right person based on context, it works better. We know internally that these four people are close to networking. If we see a networking thing, we can drill it down to those four people. If it's with this part, we can look at the commits. This is no longer a manual process internally.Jake [00:36:13]: If you go to station or help.railway.com, that's why we built it. We wanted to scale with a massive amount of leverage by aggregating feedback.Swyx [00:36:27]: This is built in-house?Jake [00:36:28]: Yep.Swyx [00:36:29]: I remember helping out on this one with Angelo in 2023. You scale a lot with a very small team.Jake [00:36:38]: Yeah. We're about 10 times bigger now.Swyx [00:36:40]: You have your full developer code here? Very cool.Jake [00:36:44]: If you go to railway.com/stats, we expose this as a pub-sub-able thing. It's all real-time metrics. There's a way to get it as JSON somewhere if you care.Jake [00:37:01]: We're big on trying to build everything in public and talk about what we're working on. We've had issues in the past, and we'll say, “Here's how we're fixing these things.” We've gotten compliments and flak for incident reports. We're always trying to make them better and talk with people.Incidents, Disclosure, and Progressive RolloutsSwyx [00:37:20]: You had a big one recently. I liked that it was scoped to 3,000. You presumably used Central Station. Talk through what happened and how you address it internally as a team.Jake [00:37:38]: Internally, this one really sucked. It had to do with an upstream provider that didn't do the behavior it said it documented, which is unfortunate given they wrote the RFC for how the behavior should work. We rolled those things out, and Central Station caught it initially when a couple users said caches weren't invalidating. We turned it off immediately.Jake [00:38:03]: When you roll out to a large user base of three million people, you get a lot of disparate behaviors. We tested in staging and had tests, but we hit an edge case. We've hardened those systems, and now we can make that better. But it was a tough one.Swyx [00:38:39]: I always wonder how private disclosure is supposed to work if people find an issue. Are they supposed to contact you first? When you run a platform, these things will happen. What channels should people pursue to quietly resolve it before it becomes a bigger incident?Jake [00:38:59]: There's responsible disclosure. We err on the side of over-disclosing and letting you know something is wrong versus having your provider gaslight you. We've erred on sharing those things more publicly, even if they impact a small subset of users. That's a decision we've made internally. We have four values. One is honor. The honorable thing is to notify people to the widest degree at which they may have been affected or there was an issue, and then confront it head-on: why did it happen, what can we do better?Swyx [00:39:45]: Not the whole user base. That's because of incremental rollouts and other things?Jake [00:39:50]: Yeah. Progressive rollouts.Swyx [00:39:54]: That should be the norm at all large platforms.Jake [00:39:58]: It should. A variety of companies do this. There's the quote that Meta runs 10,000 different versions of Meta. To our earlier point about agents, they need the same thing. They need shadow traffic and all these other things. We've built so much ceremony around production being sacred that we need to make it trivially easy to test different behaviors in a safe environment. Then you can make mistakes in a safe environment.Safe AI SRE: Customer Agents, Forked Environments, and Production ParityAlessio [00:40:30]: Do you see a world where these things get automatically caught, not necessarily by your agent, but by your customer's agent? The cache invalidation issue seems easy to check if you know to look for it.Jake [00:40:44]: It's hard because to determine it, we almost need to hook into your observability infrastructure. That's why we have the template loop on the platform: so you can roll things out progressively. You can roll out to Johnny Vibe Coder initially, or push a shard that someone consumes at their own leisure. Or you can roll it out over weeks: 0.1% of people, 1% of people, early adopters, then all the way up. That's the non-deterministic version control we talked about earlier.Jake [00:41:30]: I believe that's where most things should go, because most companies end up building staged rollout systems in-house. It's the same thing built again and again at every company. There's a massive opportunity to consolidate developer debt.Alessio [00:41:45]: You should have a free tier. Model providers give free tokens if you let them use the data. You could give free compute if someone is the number-one shard that goes out and lets you plug into their observability.Jake [00:41:55]: We do that. That's why we talked about the impact on 3,000 people. We start with lower-impact people. Larger companies on the platform are last to receive those rollouts so they have a version of the platform that's deeply stable.Alessio [00:42:16]: I have three services, so I'm sure I get the first rollout. You can nuke my thing at any time. There are all these SRE agent companies. Observability people also want agents that fix upstream problems. You have your own agent in the canvas now. How do you see that playing out?Jake [00:42:39]: It's the stacking entropy problem. If you don't have primitives to make iteration in production safe, it becomes difficult. If you're an observability provider saying, “Here's the fix to this error,” assume 80% are good and make sense. But in the last 20% long tail of complex issues, if you let somebody stamp it, you create an opportunity for an incident.Jake [00:43:08]: That's why forked environments are important. People have staging, but it always drifts from production. You need primitives, workflows, and experience built first-party on the platform so you can fork any service at any point in time.Jake [00:43:33]: I think of the canvas as a sheet of transparency paper. The agent is a little guy you push up into the canvas. It should say, “I need to copy that service and that service so I can test these two things.” It gets a read-only copy of production. Anything that's PII gets marked as a transform when we clone the database, create a copy-on-write version, or read from it. Then the agent makes changes and asks, “Does this actually work?” as close to production as possible.Jake [00:44:22]: That's how close you have to be, or you get massive drift. The system becomes unstable. You see this with massive systems built on Docker for local, Kubernetes for production, and a specific thing for something else. That complexity slows developers and becomes unstable at scale, making it hard to iterate. We want to compress that way down and say, “As close to prod as possible is where we want to be.”From AISRE Skeptic to Agent BelieverSwyx [00:45:00]: I was texting Erica for questions, and she says you were originally not a believer in AISRE. Have you come around on it?Jake [00:45:10]: I flipped, but I'm still not a believer in AISRE if you don't have the primitives to make it safe. If you unleash AISRE on production infrastructure without safe primitives for copying volumes and making sure things are fine, it's going to nuke your production database. It's not a matter of if, but when. I'm a big believer in making those loops safe.Jake [00:45:33]: I was a deep AI skeptic until 2023. In 2024, I thought, “Maybe I can roughly make this thing do it.” In 2025, I thought, “Now I can hold this.” Over winter break, everybody came back saying, “It's almost impossible to hold this.”Swyx [00:46:01]: Did you see this on the Claude docs? CloudBot? OpenCloud?Jake [00:46:06]: It's gotten to a point where it's harder to hold it wrong than to hold it right. There's a scene in Avengers where Vision picks up Thor's hammer and says it's terribly well-balanced. It self-balances and works well. I'm a deep believer at this point that this will be the dominant species: assembly, C, C++, JavaScript, words.Swyx [00:46:35]: It feels like a big jump.Jake [00:46:37]: It is. But it's not like you abandon CPU-based discrete logic and move straight to fuzzy logic. You need both. Your skills should call code or applications or some static structure. You can use skills to distill what the procedure should be or how the code should act.Jake [00:47:02]: I'm coming to a thesis: you need three points. You need a clear spec defining the system, the code, and the tests. When you say it out loud, if you've been in engineering long enough, you're like, “Of course. That's an RFC, tests, and code.” But they all matter. Having them together lets them reinforce each other: the spec and tests match, but the code doesn't, so reconcile it. Or the tests and code match but the spec doesn't, so reconcile that. That's the iteration loop.Jake [00:47:41]: That's why you're seeing people talk about software factories, docs, and reconciliation. Some of that is architectural astronomy if you don't implement it, but that loop is where most things will end up.Swyx [00:48:07]: For listeners, we've been talking about this on the pod for three years: the holy trinity of specs and tests. Itamar Friedman from Qodo is the reference if people want to look it up.Self-Modifying Infrastructure and the End of Push-Pull-RebuildSwyx [00:48:18]: One thing I want to mention on the OpenCloud idea is self-modification. I don't know how Railway would support it, but I have my OpenClaw, and I just tell it it has the Railway CLI and can do whatever. In theory, whatever capabilities or new infra it needs, it can call the Railway CLI, provision it, and add it to itself. The agent can modify its own infra.Jake [00:48:45]: It's nuts. I have a loop set up where you put the Railway CLI on top of something that runs on Railway. You're authenticated as whatever the current box is, and you can make any changes to it. Then you call Railway deploy, and it deploys itself.Jake [00:49:04]: It's like: “I need to spin up this instance of this environment. I already exist in this environment. Excellent, I have access to a Postgres instance now.” That's where we want to go with agentic, self-replicating infrastructure. That's your loop: iterate in production. You continue making changes. If it works, merge it upstream. If it doesn't, throw it away.Jake [00:49:37]: How do you make throwaway copies trivial to spin up and super cheap? The era of “I have an AWS instance with four vCPU and 16 gigs of RAM” is going to get destroyed. If you do that for agents, you need a thousand of those machines. It's prohibitively expensive compared with what we've spent a ton of time figuring out: the atomic unit of deploy, whether you call it isolates, sandboxes, or something else. Only pay for what you use, spin up instantaneously, and close the loop as quickly as possible.Jake [00:50:15]: If the system can self-replicate safely and say, “This is my environment, I'm making these changes,” it can come back with, “Does this look good? This is a new state of infrastructure given this prompt. I think I've solved it.” Then you go back and say, “Actually, it looks different.” It does the loop again. Then you say, “Cool. Apply.”Swyx [00:50:38]: That's retroactively obvious, which is the most useful kind. Any other comments on agent deployment on Railway?Jake [00:50:51]: It's getting better every day. I'm on X or Twitter. You can always yell at me about the parts not working as well as they should, because plenty of things should work way better.The New Serverless: Stateful, Long-Running, Pay-for-What-You-Use LinuxSwyx [00:51:04]: At this stage, when people want massively or embarrassingly parallel compute, they usually talk serverless. I feel like there's a new serverless compared to the previous five years of serverless. You're in that new bucket. Do you have comparisons or philosophical differences you want to call out?Jake [00:51:31]: It's somewhere in between. It's the ability to run stateful, long-running workflows or executions.Swyx [00:51:42]: Vercel has Fluid Compute, Cloudflare has some container thing, Google has App Runner and others.Jake [00:51:55]: That's where everything is roughly going, and it's why we've been working on this for six years. We believe users need access to a computer: a box that speaks Linux. They need to deploy what they want. Other systems change the surface area of what you can build. For us, users need a computer and need to deploy anything they truly want. That's why we've focused on the primitives: network, compute, storage. If we give you those and expose them so you can run things indefinitely, that's where we believe it's going.Jake [00:52:43]: Twitter has no nuance, so everyone says “servers” or “serverless.” It's always somewhere in the middle: I want to run it for a long time, but I don't want to provision the resource statically or pay for things I'm not using. That's been our thesis from day one: pay only for what you use, run it indefinitely, and it is full Linux.Swyx [00:53:12]: That's why I like the naming of Fluid. It's fluid. Flexible.Heroku, Focus, and Carrying the Torch Without Becoming the PastSwyx [00:53:18]: Another milestone is the Heroku official deprecation. You're one of the presumptive new Herokus. “New Heroku” has been a category for as long as I've been in developer tooling. It's finally happening. What was that like? Any behind-the-scenes of, “This is the moment”?Jake [00:53:42]: You have people where you're like, “You were running stuff on here? You, as this company?” It's crazy that names you would know are running on it and now coming to us saying, “We want to move a lot of this off.”Swyx [00:54:00]: Any behind-the-scenes on why Salesforce let Heroku stagnate?Jake [00:54:05]: I can only guess. It's hard when it's not your business. Salesforce's business is to build a great CRM. That's their focus. Then you acquire a compute business as an offshoot. A lot of early Meta people talk about focus. Boz has a write-up about how in the early days of Meta they had no money, so they were forced to focus. Then they turned on the money tree and had no reason not to split their focus.Jake [00:54:52]: But that dilutes your product. You get offshoots where you ask, “Is this the focus of the business?” If it's not core, it languishes. A lot of companies get in trouble when they split focus because they're fighting a multi-front war, not just externally but internally for alignment. Where are we going? What are we doing? What is our purpose?Jake [00:55:24]: If you're Salesforce-built and mission-driven, you want to work on Salesforce. Heroku is off to the side. It's not core to the business. Getting resources, budget, focus, and alignment internally becomes hard. It was a matter of time.Swyx [00:56:06]: Kudos for them to call it out instead of leaving it unknown.Jake [00:56:12]: Their release was a little odd. They called it out, but they didn't say they were shutting it down. Behind the scenes, I think they issued messages to people saying they should close accounts and that they were going to deprecate and remove things over time.Jake [00:56:30]: It's crazy because some of my first deployment experiences were on Heroku. You start with dragging things into an FTP server, then you try to get a deploy working, and then it's Heroku. It was the on-ramp for us. But the wheel turns. New things emerge. We're happy to carry the torch for a lot of that. But we don't want to be the new Heroku. We want to be the way people build and deploy software, and ultimately the way people monetize software over time.Swyx [00:57:19]: It's still a big crown to be the new Heroku. There are 50 companies that fought for that.Jake [00:57:23]: Everybody is holding some portion of it. We're happy to support people and companies. The platform works differently. The game loop is similar, but we've been dogmatic about where these things are going: primitives, agents, fan-out. Some things fit; some workflows need to change. We have an approximation of Heroku pipelines with the environment system. It's exciting. We've got a ton of people we can support, and it's growing a lot.Temporal, Workflow Engines, and State MachinesSwyx [00:58:12]: I have one more technical question about Temporal. I've sold my shares. You're a power user and one of our earliest customers. I met you through Temporal. You built on Temporal. You have complaints. This may be the most neutral and informed conversation anyone will hear about Temporal without someone working at the company.Jake [00:58:39]: That's fair. I've used Temporal for almost 10 years because of Cadence at Uber.Swyx [00:58:52]: Give people a sense of what Cadence was at Uber.Jake [00:58:57]: Cadence was the precursor to Temporal. It powers trip actions, rides, when you rent a Jump bike or scooter or car. You're running workflows for a period of time and saying, “This ride will run indefinitely until it finishes.” You attach information: you paused in this zone, so add this charge to the bill. When you end the trip, the workflow is done. That experience was powered by Cadence at the time.Swyx [00:59:34]: I used to say it's like programming the entire user journey top-down as one function.Jake [00:59:39]: It's a powerful idea and important. It's also important for the next phase of the agentic journey. You want an agent to do a specific task, be complete or incomplete on that task, and move on to the next thing. You need a way to manage workflows dynamically.Jake [00:59:59]: Temporal was always great in theory, and great when you got it working the way you wanted in production. But it required you to model the entire journey in your head. If you didn't, you could cause issues where replaying the state of the workflow causes non-determinism.Swyx [01:00:25]: Because it works on deterministic workflow history.Jake [01:00:28]: Exactly. I describe it as a jet engine. If you know how to operate it and run it, it's great. But you can't hand it to people trying to build complicated things if they don't have the whole state in their head.Jake [01:00:48]: We run our whole deployment pipeline on top of it. That's a reasonably complicated workflow: pre-commit hooks, signaling, queuing, and all the rest. We ran into the same thing at Uber. As you express a large workflow, it gets more complicated, with more states in the state machine that you have to map back to the workflow.Swyx [01:01:15]: It's a lot of ifs.Jake [01:01:16]: Exactly. At Uber, we built a system for doing the state machine and testing it. We've started to build some of those things here because it's grown heavily. It's not quite love-hate. When it works well, it works super well. But if someone who doesn't have full context puts something into the system that invalidates state or causes non-determinism, or spins off a ton of activities, you have to keep track of underlying SRE knobs like activity slots. Those should scale with memory, vCPU, and so on. It becomes a bear to scale.Swyx [01:02:10]: You need a capable sysadmin running things behind the scenes. If you moved off, what would you do?Jake [01:02:19]: We'd build our own workflow engine. We have a few internally that we've worked on.Swyx [01:02:27]: This is one of those classes of things you typically wouldn't vibe code, but I'm wondering if you can.Jake [01:02:33]: I still don't think you should vibe code it. You still want to run decent tests to make sure it works.Swyx [01:02:39]: Timo didn't invent that from scratch either. There are libraries you can run. On top of that, it's just a state machine that you have to map out. Ultimately, you define the instructions you want and run them through a state machine.Jake [01:03:00]: It's very doable. Workflow stuff is interesting. Restate is doing neat stuff here.Swyx [01:03:10]: You're tied into JavaScript. Are you a JavaScript maxi?Jake [01:03:13]: Internally, we have TypeScript, Rust, and Go. We don't add more languages. Actually, we have a little C because we write BPF code and hooks. But those are the languages.Swyx [01:03:28]: Is this for sidecars?Jake [01:03:32]: No. It's for the networking stack, volumes, and things like that. We use TypeScript a lot because it powers the dashboard, but we're moving a lot of workflow stuff off the dashboard stack and into the infrastructure stack.Railpack, Nixpacks, and Content-Addressable FilesystemsSwyx [01:04:00]: Cool. Any other technical infrastructure stuff? Railpacks?Jake [01:04:07]: We built an engine for determining dependencies based on source code. It's called Railpack. We built the first version, Nixpacks, on top of Nix, and then we moved.Swyx [01:04:17]: People have been trying to get me to adopt Nix and NixOS for four years. Is it ever going to be a thing?Jake [01:04:23]: I don't know. We're excited about it, but it has pain points. Think of it as a stack of versioned binaries at specific slices in time. If you want version X and version Y, you bloat the package space, which blows up image size and makes real-world workloads difficult.Swyx [01:04:53]: But you content-address it and cache it. In theory, there are optimizations.Jake [01:05:00]: In theory, yes. But with a large enough user base and disparate enough machines, you run into a problem Meta described in the XFAAS paper, their internal serverless system. It becomes difficult at scale unless you break out specific runtimes.Jake [01:05:24]: We didn't want to do that because we wanted to truly allow you to deploy anything. That was our initial thing with Nix. But we've moved toward interesting work around content-addressable file systems that can lazy-load anything from any point and page it into memory.Swyx [01:05:48]: Amazing.Jake [01:05:49]: The future is very bright. It's crazy, and it's going to be nuts.Coding Agent Spend, Roadmaps, and Token ROISwyx [01:05:54]: Founder journey stuff?Alessio [01:05:56]: Your cloud usage: you tweeted you're going to spend $300K this month?Jake [01:06:01]: I think we got to $200K.Alessio [01:06:02]: Coding agents?Jake [01:06:03]: Yeah.Swyx [01:06:04]: Across the company?Alessio [01:06:05]: You only have 35 people, so I'm sure they're not all spending $10K a month. What's the distribution?Jake [01:06:10]: I think I'm at about $25K. We have power users all the way down. We came back from winter break, and I basically said, “If you're writing code by hand, you're doing this wrong.” The tools are good enough now that you can move extremely quickly. There are issues and pain points, but you should be reviewing the code you are writing instead of writing it by hand.Jake [01:06:40]: Architectural patterns matter more now than ever, but you shouldn't spend your time generating code you would write. If you know how to write it, ask the agent to write it and reconcile it until it looks like you would have written it yourself.Jake [01:06:58]: People misconstrue my propensity to push people toward agents as connected to our growth and some reliability bumps. They're not necessarily related. The tools are good enough to move extremely quickly and build things way larger than you could before.Jake [01:07:19]: To the earlier point about cooling data centers in space: I don't know. But with software, you can ask, “How would I build block storage from scratch? How would I do these things?” I have ideas because I have history and have read papers. Let me work them out and build massive test benches with thousands of tests, because those are now free to author. If you're not using AI systems to speed-run your roadmap and reconcile your existing system onto the future, you're missing a large point of what's happening.Alessio [01:08:12]: What's the path to spending $3 million a month? Is it bound by ideas and things customers can absorb?Jake [01:08:19]: For most companies, it's bound by deployment at this point. That's why we've seen a massive boom in users and companies, from Fortune 50s down, asking how to get developers to move faster. You'll probably hit your CFO before any technical limits because they'll look at the eye-watering amount of money spent on tokens. Inference costs have to come down, but we're inference constrained now. There will be price discovery around what makes sense for an org to adopt.Jake [01:09:06]: I think you'll end up with the F1 driver concept. If someone is really adept at these things, it makes sense to put them in a $3 million car. If they're not, it probably doesn't make sense. You'll take a few people and say, “You can drive the F1 car. We need to go in this direction. Figure out if it works and prototype it.”Jake [01:09:33]: We've done some of that and vastly accelerated our roadmap. We thought we'd ship something in a few years; now we can probably ship it in a few months because we validated it and don't have to build it incrementally. We can skip steps and move toward our vision.Alessio [01:09:58]: A lot of people are realizing the roadmap doesn't always have a business impact, so they say tokens are too expensive. But if your roadmap were built to make more money by the time you built it, you'd have token pricing for it, the same way you do with sales. You'd spend a billion dollars on sales if you knew you would get $2 billion of revenue.Jake [01:10:19]: Exactly. A naive way to measure this is the percentage of tokens that end up in production. If you can measure impact because those tokens end up in production, that's awesome. But the burden of proof will rise. Internally, we have a growing number of pull requests that haven't merged. The question becomes: how do you get this into production? It's about how quickly you can build and deploy software, which is exciting because that's our whole thing.The SDLC Shift: Prompt Requests, Feature Flags, and Safe RolloutsSwyx [01:10:56]: The SDLC is changing. One thesis is that the pull request is dying. It's going to be the prompt request. Beyond that, code review is also kind of dying if you have all the other systems in place. What else is changing about the SDLC?Jake [01:11:19]: The AISRE and the tools to make it happen. AISRE is pie-in-the-sky aspirational. What does it take to get an AISRE? What tools do you need to build?Swyx [01:11:32]: You should expose your tooling to customers at some point. The Central Station command center.Jake [01:11:39]: We have it for template maintainers. Template maintainers can deploy and maintain templates, and they get feedback. We're going to expose those things incrementally.Swyx [01:11:51]: Clustering around incidents. Everyone has a version of that, but I don't think anyone has solved it.Jake [01:11:56]: I won't say we've solved it internally, but it's gotten so good that we can see incidents forming pretty quickly. At some point, those will be things either someone else builds or we build. We've always built things purpose-built for us. If it makes sense to make it useful for users, monetize it, or turn that loop into a profit center instead of a cost center, we want to do that.Jake [01:12:28]: Pull request is definitely dying.Swyx [01:12:29]: Do you do first-party feature flagging and incremental rollout stuff?Jake [01:12:34]: We have a feature-flagging engine we built internally and will eventually roll out.Swyx [01:12:38]: I don't see it as a user. How come you didn't give us what you have?Jake [01:12:43]: We have to beta test it. We care a lot about the quality of the things. There's plenty we've used internally that doesn't make it all the way through the journey because it fails. It works for one service but not multiple services. We'd have to build it for multiple services and know that if we released it, we'd rebuild it again and again. Some things are worth that, but many inform the roadmap.Jake [01:13:18]: We don't want to dilute the experience by saying, “This works, but only for this service,” unless it's a core initiative. Over the next few months, we'll roll out things that work for a single service, then multiple services, then multiple services across the environment. You have to be deliberate. Otherwise you create broken disparate experiences and support load because people ask how to use the feature.Jake [01:13:52]: It's the earlier expansion and compaction pattern. You expand the company to get features, then compact and smooth them out so the experience is stellar. You told me in the hallway, “It's gotten so much better.” Internally we're saying, “This part really sucks. We need to make it significantly better.”Swyx [01:14:11]: I can attest to that over the last three years watching you build Railway. For listeners, feature flagging is a huge part of Uber culture. So much so that they have too many feature flags and another thing to remove feature flags. Facebook has Gatekeeper. Agents are going to need this. It's fundamental to incremental rollouts. OpenAI acquired Statsig. GPT-5 is routing and flagging through different models.Jake [01:14:56]: It's super important. If the software development lifecycle is going to change because we're doing things 1,000 times faster and 1,000 times more concurrently, what becomes important at scale?Jake [01:15:16]: Before I started Railway, I built a feature-flagging product and tried to sell it. It was an easier version of LaunchDarkly. I ran into a problem: anyone small enough to adopt your technology doesn't care about feature flags, and anyone large enough to need feature flags needs so much scale that you have to build out all the infrastructure. I scrapped it.Jake [01:15:42]: But what is old is new again. Companies are trying to move quickly, but you can't YOLO a vibe-coded thing straight into production. You need to say, “Here's my blast radius, my impact, and I want to shadow it for these users.” Feature flags. You're going to need the tools larger companies built to maintain their structures. Everything gets compressed by 1,000x so everybody can build those structures quickly.Jake [01:16:07]: That's exactly where we are: compressing the software development lifecycle, then expanding it and adding more new things.Cattle, Pets, and Clonable InfrastructureSwyx [01:16:15]: Another term that comes to mind for newer developers is “cattle, not pets.” People treat production like a pet. It has a name. You baby it and keep it alive. With cattle, you can mass farm, roll out, portion parts out, and kill them.Jake [01:16:37]: I think that might change. You can move toward having pets as long as you have a cloning machine for your pets.Swyx [01:16:52]: Yeah.Jake [01:16:52]: If you can snapshot every single thing at every frame, it doesn't matter if something gets obliterated because you have a snapshot of it. The things we've built right now are designed to block changes from the hermetically sealed DevOps line. You have to write a Dockerfile because you nee

In the first hour of Stokely and Evans with Mark Schlereth, the Avalanche won game four against the Minesota wild last night despite how nervous Stoke was and now he owes Mike breakfast.  Sean Payton had some words of praise for second year tight end Caleb Lohner and we hear some comments from him about his coach having faith in him.  And we close out the hour by picking the brain of 9News Broncos insider Mike Klis about the Broncos opening game and Bo Nix’s ankle. 

IN THIS EPISODE– Rob Clark (“The Lone Gunman Podcast”) and Doug Campbell (“The Dallas Action Podcast”) are BACK with another fascinating marathon discussion. Among the many topics we will touch upon:A discussion of the timing of Lee Harvey Oswald's movements after leaving the Texas School Book Depository, as seen through the prism of a September of 1977 “field trip” to Dallas and Oak Cliff undertaken by members and staff of The House Select Committee On Assassinations, as recounted in a declassified report; Was Oswald trying to get to Jack Ruby's apartment?; Mae Brussell meets New Orleans DA Jim Garrison's Investigatory Staff; Why in the world would DPD Officer JD Tippit's pal Carl Mather be offered Immunity by the HSCA?; Who exactly were American mercenaries embedded in the Secret Cuban War loyal to, in the end?; The decades-long endeavor of INTERPEN & INTERPEN-adjacent individuals to implicate each other in The Hit, and– was Notorious Cuban Exile Elladio Del Valle mxxdered to keep him from talking to Jim Garrison, or because he DID actually talk to Garrison?PLUS– More creepy creepiness that proves David Ferrie was indeed creepy, the lawsuit against The Federal Government by the heirs of Orville Nix, Jr. continues to gain steam, and Peter Tork monkeys around with hippie chicks.JOIN US!Written & Hosted by Rob Clark & Doug Campbell.Recorded and Engineered by Momo Scaranucci, Jr. for Drop-D Podcast Productions.  Become a supporter of this podcast: https://www.spreaker.com/podcast/quick-hits-the-jfk-assassination--3682240/support.

Welcome back into the Dynasty Nerds podcast as Garret Price and Andrew Mott complete the offseason circle—after buy targets, it's time to talk sells. And they're clear up front: “sell” doesn't mean a player is bad. It's about price, roster build, and whether you can pivot within a tier without sacrificing your title chances. Listen to This Episode: Apple Podcasts Spotify YouTube Andrew opens with Trevor Lawrence as a classic “tier-down” candidate. The market is pricing him like a top-10 dynasty QB off a scorching 2025 second half, but the guys argue the gap between Lawrence and steady producers like Purdy, Dak, Nix, or Goff isn't big enough to justify the premium. The ideal move is staying in the same QB tier while adding a throw-in on top. Garret brings the heat with Trey McBride—not because he's not elite, but because he might be at peak value. The argument: if you can flip McBride into Brock Bowers, you take the better long-term target environment. McBride's situation carries more “yellow flags” (changing offense, more target competition, potential QB shifts, and a run-game emphasis) that could shave his weekly edge and turn a “$1” asset into an “$0.85” asset quickly. Start Using the Film Room Today! FFPC: New Users: Use promo code NERDS for $25 off your first FFPC Orphan Team! 00:00 Start 01:41 Sell Trevor Lawrence 05:30 Sell Trey McBride 11:47 Sell Christian McCaffery 17:01 Sell DeVonta Smith 21:48 Sell Kyren Williams 27:07 Sell Lamar Jackson Learn more about your ad choices. Visit megaphone.fm/adchoices

In hour 3 of The Drive, Zach and James debate if Avalanche head coach Jared Bednar made a mistake by muddying the waters by pulling Scott Wedgewood at goaltender during Game 3. We hear from Bednar on not announcing a starting goaltender in tonight's Game 4. How much is Wedgewood to blame for allowing 3 goals during his time in net? How many times can Bednar pull the lever of changing goalies, and can he go back to Wedgewood if Blackwood starts tonight and doesn't play well? The guys break down Josh Kroenke's season-ending press conference from last week and voice their dislikes from his comments. We hear from Josh Kroenke, calling himself the "Chief Culture Officer", and Zach points out the irony of Josh not being in the building on a day-to-day basis. We recap the Broncos' rookie minicamp and what Sean Payton had to say about the group they had at practice. We hear Sean Payton's update on Bo Nix's ankle and debate if Nix will be ready to roll for the Broncos' offseason program. What are the guy's level of concern with Nix's ankles moving forward?

In hour 2 of The Drive, Zach and James continue their conversation on the Nuggets and Josh Kroenke labeling himself as the "Chief Culture Officer". Did Kroenke not set the expectation of the Nuggets as a championship or bust team? We pivot to the Broncos and discuss Sean Payton's update on Bo Nix's ankle. Will Nix be ready to roll for the Broncos' offseason program? Is there reason to be concerned with Nix's ankles moving forward? Today's "Three Count" features a look around the NHL and NBA playoffs, both the Philadelphia Flyers and 76ers getting swept in the second round of their playoff runs, and our reaction to the NBA Draft Lottery results. We dive back into the Avalanche and their disappointing Game 3 loss on Saturday. Did the Avs let the Wild back in the series with their win? Do the Avalanche have the right leadership to refocus and have a better approach in Game 4? 

00:00 High Five: Blackwood starting, Nix's ankle, Aaron Rodgers, Giannis trade calls, Wemby elbow.

For a quarterback who willed his team to the AFC Championship game, Bo Nix isn't getting the credit he deserves. How could national pundits have watched last season and think that Nix was anything other than the real deal? Most importantly, why do Broncos fans care? Mike and Jess take a look at this and much more in this week's Something Something Broncos.

Hour 1 of The Drive kicks off with Zach and James cross-talking with Dover and Cecil. The guys discuss the high-scoring first game between the Avalanche and Wild in the second round of the playoffs. Will the Avs debate benching Scott Wedgewood for Mackenzie Blackwood after allowing 6 goals in a win? Zach and James continue to break down the Avs and Wild, wild game 1. Who is to blame for the Avs allowing 6 goals in the game? Does Wedgewood deserve the benefit of the doubt to start game 2? How historic was the Avs' offense in last night's game with 4 different defensemen scoring 5 goals total? What did the guys make of Marty Necas's performance with three assists but no goals? The guys react to Bo Nix's recent Instagram post, which features a video of him running at the Brocnos practice facility. The guys speculate when this video was taken and what shape Nix is in now. 

In hour 4 of The Drive, Zach and James finish their conversation on Bo Nix posting a video of himself running at the Broncos practice facility. Who is Nix trying to convince of his health by posting this video? We pivot to the Nuggets and discuss the latest reporting regarding the Nuggets being open to re-constructing the roster. How do the guys feel about Aaron Gordon being a trade candidate for teams like the Lakers, Suns and more? What kind of returns would the Nuggets get for players like Gordon, Murray and Braun? Are the Nuggets making a mistake by bringing back Adelman for a second year and potentially wasting more of Jokic's prime? Is the Nuggets' ownership not maximizing their championship window by not being willing to spend on front office executives? We wrap up the show with Zach sharing about his experience at the Avalanche Game 1 last night with his family. 

In hour 2 of The Drive, Zach and James finish their discussion on Bo Nix posting a video of himself running at the Broncos practice facility. Is Nix's video misleading as many think this video is from months ago or even a year ago? Who is Nix trying to convince with this video? We pivot to the Nuggets and discuss ESPN's Shams Charania's recent reporting on the Nuggets keeping David Adelman but being open to making moves with the roster outside of Nikola Jokic. Are the Nuggets making a mistake by bringing back Adelman for a second year and potentially wasting more of Jokic's prime? Today's "Three Count" features the Nuggets' ownership not maximizing their window after not being willing to spend on front office executives and coaches, Joel Embiid exercising some demons by beating Boston in game 7 to move on to the second round, and Skip Bayless joining Stephen A. Smith on First Take this Friday. We dive into the reports on Aaron Gordon being looked at as a trade candidate for teams like the Lakers, Suns, and more. 

Meet Spring and Nix or "Sprix" as they are called together. These foxy sex party veterans embarked on an adventure at a religious themed event that became a team sport. Somewhere in Mormon heaven, Joseph Smith and Brigham Young are high-fiving each other. If you would like to tell us about a high-five-worthy sexscapade, write it up, and send it in to Q@Savage.Love! This episode is brought to you by VB Health, Doctor-formulated supplements that work . To learn more about Load Boost, Drive Boost and Soaking Wet and to get 10% off, visit VB.Health when you use the code Savage.

In hour 2 of The Drive, Zach and Phil take a deep dive into the Nuggets as they get set to face off with the Timberwolves in an elimination game in Game 6. Will we see Aaron Gordon suit up for the Nuggets tonight? Is this version of Gordon a better option than Spencer Jones? Who is the X-Factor for the Nuggets tonight? Will we see Cam Johnson continue his success from Game 5? We pivot to the Broncos and hear from Mike Klis on Bo Nix's surgery and what his timeline will look like heading into OTA's. What will Nix miss if he is unable to participate during OTA's? Today's "Three Count" features the odd similarities of the Broncos final pick in the draft and Khalil Mack, local legend Calais Campbell signing a one-year contract with the Ravens at the age of 39, and previewing the Wild and Stars game 6 tonight. We hear from Jarde Bednar and his thoughts on the style of hockey played in the first round and how that will look moving forward in the playoffs. 

In the 3rd hour, Dover and Cecil previewed tonight's Nuggets game against the Timberwolves. What do the Nuggets need to do to force a Game 7 Saturday night? The guys heard from Jared Bednar on if he's learned anything from watching the Wild-Stars series as the team waits to play one of them in the second round. Is the Bo Nix ankle injury a bigger issue than we realized? The guys discussed why the Broncos need to add another backup QB to have behind Nix. 

In hour 3 of The Drive, Zach and Phil dive into the news of Bo Nix going in for another procedure on his ankle after his previous ankle surgery this offseason. How concerned are the guys with Nix's history of ankle issues? Did Nix have a setback? Will this be something that pops up throughout Nix's time with the Broncos? How impactful is it that Nix will likely miss OTA's? How willing will the Broncos be to give Nix a mega contract extension after this season? We react to Justin Simmons calling it a career and retiring as a Bronco. Phil shares about his time as a teammate of Simmons and how he was a bright spot during a dark time in Broncos' history. Does Simmons deserve to be a Broncos Ring of Famer? We preview the Nuggets and Timberwolves game 6. What adjustments will Minnesota make to counter the Nuggets' blowout win in game 5? 

In hour 2 of The Drive, Zach and Phil take a deep dive into Bo Nix going in for another ankle surgery this offseason. What is the concern level for Nix after he went in for his 5th surgery on his ankle? Will this be a recurring issue for Nix during his time with the Broncos? Is it fair to label Nix as "injury prone"? Should the Broncos be interested in Aaron Rodgers if Nix is unable to start the season healthy? Today's "Three Count" includes Phil's answer on whether the Broncos should bring in Aaron Rodgers, a reaction to the Rockies losing to Cincinnati 7-2 yesterday, the NCAA expanding its tournament to 76 teams, and the Spurs moving on to the second round of the playoffs. We look into the Wild and Stars series as we get closer to knowing who the Avalanche will take on in the second round of the playoffs. We hear from Erik Johnson and his thoughts on the Avs' struggling power play. Did Scott Wedgewood get snubbed after not being announced as a Vezina Award finalist? 

In hour 4 of The Drive, Zach and Phil take a deep dive into Bo Nix going in for another ankle surgery this offseason. What is the concern level for Nix after he went in for his 5th procedure on his ankle? Will this be a recurring issue for Nix during his time with the Broncos? Is it fair to label Nix as "injury prone"? How willing will the Broncos be to give Nix a mega contract extension after this season? Should the Broncos be interested in Aaron Rodgers if Nix is unable to start the season healthy? How impactful is it that Nix will likely miss OTA's? We wrap up the show with DenverSports.com's Will Petersen joining the show to discuss Bo Nix's additional procedure on his ankle this offseason, if Nix had a setback during his ankle rehab, and if there is smoke with Aaron Rodgers joining the Broncos. 

Hour 1 of The Drive kicks off with Zach and Phil cross-talking with Dover and Cecil. The guys discuss the news of Justin Simmons retiring from the NFL, and we relive how professional he was with the Broncos during a down period in the franchise's history. Zach and Phil dive into the news of Bo Nix going back under the knife after his ankle surgery earlier in the offseason. Did Nix have a setback from his surgery? Is it time to stop defending Nix's history of ankle issues and start being concerned? We break down the final Broncos draft picks from last weekend. Today discussing Miles Scott, Dallen Bentley, and Red Murdock. We react to Justin Simmons calling it a career and retiring as a Bronco. Phil shares about his time as a teammate of Simmons and how he was a bright spot during a dark time in Broncos' history. Does Simmons deserve to be a Broncos Ring of Famer?

In the 3rd hour, Dover and Cecil discussed if they're concerned about the latest developments of Bo Nix's newest procedure on his ankle. The guys heard from Nix after the season saying it was going to be an easy surgery and recovery. What's the latest injury news surrounding Josh Manson of the Avs? The fellas talked about how the Broncos sent a message to Evan Engram by drafting two TEs in this year's draft. 

Study Guide: Day 3 Terry Stops, Special Needs, and the Exclusionary RuleMastering the Fourth Amendment: From Stops to SuppressionThis episode offers a comprehensive breakdown of the core principles governing police searches and seizures under the Fourth Amendment. Whether it's understanding Terry stops, special needs searches, or the exclusionary rule, you'll gain clear insights into how constitutional law balances law enforcement interests and individual rights.Most police encounters are governed by a complex hierarchy of suspicion—from minimal to probable cause. But what happens when officers operate without that VIP status—when suspicion is mere guesswork or absent altogether? The answer lies in the Fourth Amendment's often-misunderstood doctrine of special needs searches, a regulatory workaround that dramatically shifts the constitutional landscape.This episode pulls back the curtain on the rules and limits that affect searches of your body, vehicle, home, and even the schoolyard. You'll discover how the landmark Terry v. Ohio case revolutionized policing by allowing brief stops based on reasonable, articulable suspicion—a concrete, objective standard that balances investigative needs against individual rights. We dive into the specifics of stop-and-frisk, what qualifies as a valid Terry stop, and how courts measure duration and scope to prevent abuse.We break down the opaque world of special needs searches—like sobriety checkpoints, drug testing in schools and workplaces, and inventory searches—focusing on when the government can override traditional warrants and probable cause. Expect to understand how the primary purpose test determines if a search is justified, and why border searches and suspicionless inspections are still constitutional under this framework.And it wouldn't be complete without a deep look at the exclusionary rule, the powerful mechanism designed to deter illegal searches by suppressing unlawfully obtained evidence. You'll learn about the fruit of the poisonous tree, and the critical exceptions: independent source, inevitable discovery, and attenuation. We analyze real case studies—like the tragic Williams and Nix cases—to see how courts balance justice versus police misconduct.Why does it matter? Because police overreach and constitutional violations threaten the integrity of justice. But unchecked exclusion can let dangerous criminals walk free, raising questions of societal cost versus constitutional principle. Understanding this intricate dance arms you with the insight to analyze real-world issues—from surveillance to school policies, to border control—like a seasoned expert.Perfect for law students, attorneys, or anyone wanting a clear, comprehensive grasp of Fourth Amendment limits and their practical effects. If you're preparing for the bar or criminal procedure exam, this episode gives you the analytical tools to identify violations, apply exceptions, and craft compelling legal arguments—whether in the courtroom or on your next practice exam.In this episode:The evolution from binary probable cause standards to the nuanced ladder of suspicionThe distinctive requirements for reasonable suspicion and the limits of Terry stopsHow the plain view doctrine and the scope of frisking maintain officer safety without infringing privacyThe special needs doctrine's exceptions, including sobriety checkpoints, drug testing, and border searchesThe critical distinction between suspicion-based searches and suspicionless, administrative searchesThe complex rules surrounding inventory searches and how they can be exploitedThe purpose, limits, and exceptions to the exclusionary rule, including independent source and inevitable discovery doctrinesKey case law, including Terry v. Ohio, Mi

In this episode, Ray Cochrane unpacks Anthropic’s Mythos model and the Treasury’s emergency meetings with Wall Street, then digs into Apple’s vibe-coding crackdown and a gaming-anxiety study that hit way too close to home. Also covered: Verge’s solid-state motorcycle, UBTech humanoid robot sales jumping 23-fold, Japan’s first osmotic power plant, Finland’s permanent nuclear waste vault, Ghostty landing in Ubuntu, Cloudflare’s EmDash CMS, and a Claude Code skill that talks like a caveman. – Want to start a podcast? It’s easy to get started! Sign up at Blubrry – Thinking of buying a Starlink? Use my link to support the show. Subscribe to the Newsletter. Email Ray if you want to get in touch! Like and Follow Geek News Central’s Facebook Page. Support my Show Sponsor: Best Godaddy Promo Codes Get 1Password Full Summary Cochrane opens the show by framing Anthropic’s new Mythos model as the AlphaGo moment for cybersecurity. From there, the episode moves through Apple’s pushback against AI-generated apps, a gaming anxiety study with a deeply personal hook, a series of “first to ship” energy and robotics wins out of Finland, China, and Japan, and several developer-tool stories that show how quickly the economics of software are shifting. Mythos, the Detection Ceiling, and Wall Street’s Emergency Response Anthropic’s Mythos model has Wall Street rattled. Operating autonomously, Mythos found and demonstrated the exploitation of a 27-year-old TCP SACK bug in OpenBSD, an operating system famous for being one of the most security-focused on the planet. Per Anthropic’s red team, over 99% of the vulnerabilities Mythos has identified remain unpatched. The researchers’ conclusion is blunt: “the moat in AI cybersecurity is the system, not the model.” The policy response moved fast. On April 7th, Treasury Secretary Bessent and Fed Chair Jerome Powell pulled the CEOs of Goldman Sachs, Citi, Bank of America, and Morgan Stanley into Treasury headquarters on short notice. All four banks are now testing Mythos internally. Treasury CIO Sam Corcos is also seeking direct access. Anthropic is gating distribution through Project Glasswing, a limited-access program with JPMorgan, Apple, Google, Microsoft, and Nvidia. Cochrane comes down firmly behind Anthropic’s gated approach. Because a 5.1-billion-parameter open model can apparently recover the core analysis chain for the OpenBSD flaw, this capability is not locked behind Frontier Compute. He wants the critical infrastructure hardened before the public gets keys. However, he also notes the bigger lesson is about human wisdom: people offloading all their thinking to AI lose out on the wisdom that makes any of these tools genuinely useful. Apple Bans Vibe Coding Apps from the App Store Apple has been quietly pushing back against what people are calling “vibe coding” apps. Replit, Vibecode, and an app called Anything all run AI models on the phone and produce working software that runs inside the host app. Apple cites Guideline 2.5.2, in effect since 2017, which requires apps to be self-contained. Replit and Vibecode had their App Store updates blocked. Anything was pulled in late March, briefly restored on April 3rd, and then pulled the same day again. The forcing function is volume. App Store submissions jumped 84% in a single quarter as vibe coding tools flooded Apple’s review queue with AI-generated apps. Cochrane thinks Apple is justified, given the security issues swirling around the Vibe coding ecosystem. Even a beautiful diamond gets lost in a sea of sand, and that flood is exactly what Apple is trying to manage. The company behind Anything is now pivoting to iMessage, desktop, and Android. Playing Video Games to Win Is Linked to Higher Anxiety Cochrane gets personal on this one. Through high school and his early 20s, he was deeply addicted to League of Legends. His dad teased him about it constantly. In the last few years of that addiction, his body would go ice cold and shake every ranked match before. His partner identified it as a panic attack. The moment that happened, he quit. Today, he no longer shakes. The new study lines up with his experience. Researchers Kayleigh Watters and Mikael Rubin at Palo Alto University analyzed a publicly available database of 13,464 adult gamers, most of whom primarily played League of Legends. Players who game to win show higher generalized anxiety but actually play fewer hours, since performance pressure pushes them out. Players who game to relax show strong links between social anxiety avoidance and more hours played. The study appeared in the Journal of Affective Disorders. The headline framing of “playing to win makes you anxious” misses the point. The real finding is more interesting: gaming for avoidance and gaming for competition are both warning signs, for different reasons. Cochrane notes that the League of Legends community’s toxicity has been a running joke for years, and this study suggests the game’s structure may have been manufacturing the anxiety that fueled it. Sponsor: GoDaddy Economy hosting is $6.99/month, WordPress hosting is $12.99/month, and domains are $11.99. Both hosting plans include a free domain, professional email, and SSL certificate. Go to geeknewscentral.com/godaddy for the best pricing and to directly support this independent show. Verge Motorcycle: World’s First Production All-Solid-State Battery Cochrane filled his tank for $60 today, which made this story land especially hard. His mom has driven electric for years and patiently manages a 90-mile real-world range. The next-generation answer is already shipping. Verge Motorcycles, a Finnish company, is the first production vehicle of any kind with an all-solid-state battery. Their 2026 bikes ship in Q1 with a pack from Donut Lab, another Finnish outfit spun out of Verge. The numbers are bonkers. The pack delivers an energy density of 400 Wh/kg, roughly double that of current Tesla cells. It sustains 100kW charging, hits full charge in about 5 minutes in the lab and 12 minutes on the actual bike, and the long-range version covers 600 kilometers (about 370 miles) per charge. Toyota, QuantumScape, and Samsung SDI have all been telling us that solid-state is coming in 2027 to 2030. A Finnish motorcycle company shipping in Q1 2026 just embarrassed them all. UBTech Humanoid Robot Sales Jump 23-Fold UBTech dropped its 2025 annual earnings on April 1st. Humanoid robot revenue hit 820 million yuan, roughly $119 million USD, up 2,203% from 35.6 million yuan the year before. Unit sales went from 3 robots in 2024 to 1,079 in 2025. Shares jumped 14% on the announcement. The customer list is a real industrial deployment: BYD, Foxconn, Geely, FAW-Volkswagen, and Audi. The flagship is the Walker S2, with UBTech targeting 5,000 units in 2026 and 10,000 in 2027. Cochrane is honest about what this means. He does not think we are heading for an extinction event, but worker displacement is a real concern. The US has no universal income or universal healthcare. The people affected are not white-collar managers. They are everyday line workers who already make the least on the ladder. Work efficiency reportedly doubles when these robots arrive, which is a company-side win, but the humans they replace are not getting half a year of gardening leave to retrain. He invites the listener to take on this one directly. Japan Switches On Asia’s First Osmotic Power Plant In August 2025, Fukuoka’s Seawater Desalination Center quietly opened Asia’s first osmotic power facility. It generates about 880,000 kilowatt-hours per year, enough for roughly 220 homes. It is only the second operational osmotic plant in the world, after Mariager, Denmark, in 2023. Osmotic generation uses a salinity gradient: fresh water on one side of a membrane, salt water on the other, and the pressure difference spins a turbine. The clever part is what Fukuoka does with desalination brine. Instead of regular seawater, the plant uses concentrated brine left over from the desalination process. This amplifies the salt gradient and squeezes more energy out of the same membrane. The result is a closed-loop partnership: the desalination facility produces drinking water and leaves brine behind, the osmotic plant turns the brine into electricity, and that electricity runs the desalination facility. Every desalination plant on Earth produces brine, so if Fukuoka’s co-located model works, the same pattern could be replicated across hundreds of plants worldwide. Japan’s Luna Ring Solar Moon Proposal Goes Viral Again Shimizu Corporation’s Luna Ring concept is making the rounds again. The pitch: a 6,800-mile belt of solar panels around the Moon’s equator, beaming microwave power back to Earth. Project lead Tetsuji Yoshida has long argued that a full ring could eliminate fossil fuel dependence entirely. The proposal first surfaced in 2013, has no funding, no government endorsement, and no concrete cost estimate. Shimizu has not put any active development behind it. Cochrane finds the concept fun every time it resurfaces. However, this would have to be a worldwide effort in the truest sense, with treaties, a new generation of launch economics, and microwave power transmission at a scale nobody has demonstrated. Beaming the power back to Earth has always been one of the biggest practical holdbacks. The Luna Ring is inspirational, but not shipping. Finland’s Onkalo Nuclear Waste Vault Opens Finland’s Onkalo facility is the world’s first permanent deep geologic repository for spent nuclear fuel. Operated by Posiva, the facility is buried about 430 meters down in 1.9-billion-year-old bedrock. It is designed to hold up to 6,500 tons of spent fuel and operate until the 2120s. The construction costs about €1 billion, with operating and closure adding roughly €4 billion more before the program is done. The catch is that radioactivity remains dangerous for hundreds of thousands of years. Edwin Lyman, director of nuclear power safety at the Union of Concerned Scientists, warned that the copper canisters will eventually corrode, with different scientific opinions on how fast. Geologic disposal remains “fraught with uncertainties,” and we have never validated an engineered system across a 100,000-year time frame. The bet is that the rock and copper outlast the radioactivity. Cochrane sees Onkalo as time-buying rather than a final answer. It is more of a bank holding spent fuel while science catches up. He prefers it to Japan’s ongoing approach of releasing tritium-treated water from Fukushima Daiichi into the Pacific, even though the dilution is well below WHO drinking water guidelines. Burying the waste in an insurmountable containment strikes him as the more honest answer to a problem nobody knows how to truly solve. Ghostty Terminal Lands in the Ubuntu Repos Ghostty 1.3.0 is now available in Ubuntu 26.04 LTS’s universe repository. The install is simply `sudo apt install ghostty`, no PPAs, no Snap, no Nix, no building from source. Ghostty was created by Mitchell Hashimoto, co-founder of HashiCorp. It is GPU-accelerated, uses native Swift on macOS and native GTK4 with libadwaita on Linux, and supports tabs, splits, profiles, ligatures, and the Kitty graphics protocol. Cochrane recently caught Hashimoto on a podcast, where he walked through his agentic coding workflow. Ghostty is being actively built using AI harnesses like Claude Code and Codex. Hashimoto told a story in which Codex fixed a six-month-old bug in 45 minutes, for a total API cost of $4.14. Personally, Cochrane uses WezTerm, but he is excited to see Ghostty become more widely available with a native UI rather than Electron. Borgo: Rethinking Go Using Rust Analytics India Magazine profiled Borgo, a programming language by developer Marco Sampellegrini (GitHub: alpacaaa). Borgo is statically typed with Rust-like syntax, but it compiles to Go and uses the Go runtime and garbage collector. It includes sum types (Option and Result), pattern matching, and full compatibility with existing Go packages. Notably, it removes Rust’s borrow checker and lifetimes entirely. Borgo is not new. It first appeared on Hacker News in 2023, with a RustLab talk in 2024. The 2026 angle is a renewed look at it through the lens of AI coding agents, since type-rich languages like Rust have been showing outsized productivity gains. Cochrane is a fan of Rust and stands by the borrow checker, but he enjoys these exploratory languages for what they reveal about what developers actually want. Caveman: A Claude Code Skill That Cuts 65% of Tokens Developer Julius Brussee built a Claude Code skill called Caveman that forces Claude to respond in stripped-down fragments. No articles, no “just,” no “really,” no pleasantries, no hedging. The tagline is “why use many token when few token do trick.” Across 10 real dev tasks, Caveman mode averaged 294 tokens per response, compared to 1,214 in normal mode. That is a 65% drop in output tokens. The project is MIT licensed with three intensity levels: lite, full, and ultra. Cochrane stumbled across the project online and shared it with a classmate who had been complaining about token costs. The classmate now insists that “the caveman is the only way to live.” Cochrane has not made the switch, but the bigger point lands. If a community plugin can cut 65% of tokens without correctness regressions, the labs are shipping verbose-by-default and charging users for the privilege. He suspects verbose output makes models feel more trustworthy, even when the token math says otherwise. Cloudflare Launches EmDash as a WordPress Successor Cloudflare released EmDash on April 9th, an open-source, MIT-licensed, TypeScript-based CMS pitched as the spiritual successor to WordPress. The big flex is that it was built in 60 days using AI coding agents. EmDash runs on Astro 6.0, either on Cloudflare’s edge platform or on a standard Node.js server. The plugin security model uses sandboxed Dynamic Workers with explicit permissions, addressing the architecture flaw that Cloudflare says causes 96% of WordPress vulnerabilities. Cochrane could not resist pointing out the irony of the name. The em dash has become the trademark giveaway that an AI was involved in writing. He has reservations about whether EmDash will succeed. WordPress is extremely hard to unseat, plenty of “WordPress killers” have come and gone, and the ecosystem is twenty-plus years deep. He is curious to see what comes next but not optimistic. Google Open-Sources the DESIGN.md Format Google Labs open-sourced the DESIGN.md format used by Stitch, their AI UI design tool. DESIGN.md is a declarative file capturing a project’s design system, colors, typography, and spacing in a way AI agents can read and apply. Cochrane has tried Stitch personally and finds it impressive at producing web designs. He has also seen DESIGN.md-style files already start appearing in repositories. He sees this kind of file becoming a new paradigm for agentic design, alongside robots.txt and llms.txt. However, he worries about a side effect. If everyone uses the same standardized format and the same AI tools, the web could become a homogeneous set of sites that all look the same. He is enthusiastic about the standardization but hopes designers continue to push for genuinely unique work. A 13-Liter PC With a Water Loop Built Into the Case Geeky Gadgets covered a build by “Visual Thinker”, a 13-liter mini-ITX case with custom SLA-printed water distribution plates built directly into the chassis. Instead of traditional soft tubing, plates channel coolant between the CPU and GPU blocks and are sealed with TPU and silicone molds. The case supports a full-size GPU and an SFX power supply. No thermal benchmarks, parts list, or pricing have been published. It is a one-off you cannot buy. Cochrane sees this as a sign of where PC building has gone in 2026. Modern mid-grade GPUs run nearly every recent game, so raw performance is no longer the differentiator. He likes seeing builders lean into design and craft rather than just stuffing the most powerful parts into a box. He admits he is the traditional type and built his own machine to maximize parts, but the design-first direction is a healthy evolution for the hobby. To close out the show, Cochrane recommends Pocket Casts as a podcast app. He finds it picks up new episodes very quickly. Big thanks to GoDaddy for over twenty years of keeping this show on the air, and a reminder that every promo code use is like writing a check to the show. The post Mythos: Cybersecurity’s AlphaGo Moment #1862 appeared first on Geek News Central.

This Day in Legal History: Nix v. HeddenOn April 24, 1893, the U.S. Supreme Court received submissions in Nix v. Hedden, the famous case asking whether a tomato should be treated as a fruit or a vegetable. The question sounds like the setup to a joke, but the legal issue was practical and financial: under the Tariff Act of 1883, imported vegetables were taxed, while fruits were not.That meant the classification of tomatoes had real consequences for importers bringing tomatoes into the United States. The plaintiffs argued that tomatoes are fruits in the botanical sense because they grow from the flower of the plant and contain seeds. The government argued that, whatever botanists might say, tomatoes were commonly bought, sold, cooked, and eaten as vegetables.The Supreme Court sided with the government. In its decision, the Court held that the tariff law should be read according to the ordinary meaning of the words “fruit” and “vegetable,” not their technical scientific meanings. Justice Horace Gray explained that tomatoes are usually served with dinner, not dessert, and are understood in common speech as vegetables.The case became a lasting example of how courts interpret statutes by looking at the way language is used in everyday life. It also shows that legal disputes often turn less on abstract definitions than on context, usage, and consequences. Nix v. Hedden remains memorable because it turns a simple grocery-store question into a lesson about statutory interpretation: the tomato may be a fruit to a botanist, but for tariff law in 1893, it was a vegetable.Federal prosecutors in Manhattan have charged U.S. Army Sgt. Gannon Ken Van Dyke with allegedly using classified information to profit from prediction-market bets tied to a military raid involving former Venezuelan President Nicolás Maduro. Van Dyke, who was stationed at Fort Bragg in North Carolina, allegedly helped plan and carry out the operation that resulted in Maduro and his wife, Cilia Flores, being brought to New York in January.Prosecutors say he began trading on Polymarket markets related to Maduro and Venezuela on Dec. 26, 2025, shortly before the Jan. 3, 2026 raid. According to the indictment, Van Dyke made more than $400,000 from those trades. The government alleges that, after making the money, he tried to hide the proceeds. He is charged with violating the Commodity Exchange Act, wire fraud, and making an unlawful monetary transaction. The Commodity Futures Trading Commission also brought a related enforcement action against him. Van Dyke was expected to appear first in federal court in North Carolina before later appearing in the Southern District of New York. Counsel information for him was not immediately available.Soldier Aware Of Maduro Raid Bet On Polymarket, Feds Say - Law360U.S. District Judge Esther Salas warned that proposed federal data privacy legislation could undermine state laws meant to protect judges and other public officials from having their personal information exposed online. Salas has pushed for stronger privacy protections since 2020, when a lawyer went to her New Jersey home and killed her 20-year-old son, Daniel Anderl. Congress later passed the Daniel Anderl Judicial Security and Privacy Act, which shields federal judges' personal information online. Since then, more than a dozen states, including New Jersey, New York, and Maryland, have adopted similar protections for state judges, and some laws also cover law enforcement officers, prosecutors, and family members.Salas raised her concerns at an American Bar Association conference in Boston as House lawmakers consider federal privacy bills that would create national standards and preempt state laws. The bills, called the GUARD Financial Data Act and the SECURE Data Act, would require covered companies to limit collection of consumer data and give people rights to access or delete their information. But unlike New Jersey's Daniel's Law, the federal proposals would not let individuals sue companies for privacy violations. Salas said replacing stronger state protections with weaker federal rules could put judges across the country at greater risk. House committee representatives either declined to comment or did not respond.NJ judge whose son was killed warns against weakening state data privacy laws | ReutersSpirit Aviation told a New York bankruptcy judge that it is in advanced talks with the federal government over a major financing package that could help keep its second Chapter 11 case on track. The airline's lawyer, Marshall Huebner of Davis Polk, confirmed that negotiations are underway but did not verify reports about the possible size of the package or whether the government would receive an ownership stake. He said the proposed funding could do more than simply support the bankruptcy case and could position Spirit to compete strongly after restructuring. Spirit plans to seek court approval of the financing on April 30.The financing discussions come after the war involving the U.S., Israel, and Iran caused jet fuel prices to rise sharply, disrupting Spirit's existing reorganization plan. The airline had previously proposed canceling general unsecured claims and restructuring around support from secured noteholders, but it postponed seeking approval to send that plan to creditors. Judge Sean Lane approved a $533 million sale of about 20 aircraft to CSDS Aircraft and also granted Spirit a 90-day extension of its exclusive right to file a Chapter 11 plan. Spirit also disclosed that it missed an interest payment, triggering a default under its debtor-in-possession loan. The noteholder group funding much of that loan said it intends to enforce its rights and would oppose any relief that harms the lenders.Spirit In ‘Advanced' Talks With Gov't For Ch. 11 Financing - Law360 This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.minimumcomp.com/subscribe

In hour 4 of The Drive, Zach and Phil take a deep dive into the Nuggets as they get ready to go on a championship run. Is this year's team better than the 2023 team that won the title? We hear from Anthony Edwards on the rivalry between Minnesota and Denver, Julius Randle's thoughts on what he's learned about playing against Jokic, and Chris Finish's thoughts on slowing down Jokic. We react to Bo Nix's letter he wrote to his newborn daughter. Zach reads excerpts from the letter and points out the new side of Nix he saw when openly and honestly talking about his personal life. We wrap up the show with DenverSports.com's Will Petersen joining the show to discuss Nix's letter in the Player's Tribune and what we learned about Nix. 

Oh nein! Es brennt! Was mache ich bloß? Unterirdisch im Bau verstecken? Fliehen? Oder sogar: Juhu! Nix wie hin!? Tiere reagieren sehr unterschiedlich auf Feuer. Viele haben wahre Superkräfte um ein Feuer rechtzeitig wahrzunehmen und zu fliehen. Einige zündeln aber sogar und legen Buschbrände, um genau diese vor dem Feuer fliehenden Tiere zu erbeuten. Andere legen ihre Eier nach einem Brand gezielt in die noch glimmenden Stämme von Bäumen.Die Anpassungen, die Tiere an Feuer in der Natur entwickelt haben, sind mal wieder mindblowing. Einige dieser seit Jahrtausenden erprobten Strategien funktionieren heute aber nicht mehr richtig, da sich die Art und Frequenz der Feuer durch uns Menschen ändert.So werden Brände auf einmal wirklich brandgefährlich. Für ein Ökosystem und am langen Ende für den Planeten.Wir danken unserem edlen Spender für die Unterstützung und den coolen Folgenwunsch!Auch ihr könnt uns unterstützen:Ihr könnt unseren Podcast für die Kategorie Audio beim UmweltMedienpreis nominieren! Geht ganz schnell und wir sind ewig dankbar: https://www.duh.de/events-aktionen/umweltmedienpreis/nominierung/Unser Podcast ist weiterhin Community finanziert. Unterstützt uns unter: https://steady.page/de/tierisch/aboutWeiterführende Links: Feueranpassung und Klimawandel: https://www.nationalgeographic.com/environment/article/wildfires-pyrocene-climate-change-animals-adaptationsLeben wir im Pyrozän? https://aeon.co/essays/the-planet-is-burning-around-us-is-it-time-to-declare-the-pyroceneEchsen und Feuer: https://zslpublications.onlinelibrary.wiley.com/doi/10.1111/jzo.12545Der Emu Wren: https://www.dcceew.gov.au/environment/biodiversity/threatened/species/20-birds-by-2020/mallee-emu-wrenEinfluss von Rauch auf Wildtiere: https://www.nationalgeographic.com/animals/article/how-does-wildfire-smoke-affect-wildlife Hosted on Acast. See acast.com/privacy for more information.

Aaron and Derek welcome back horror comic author extraordinaire Cullen Bunn (Harrow County, The Empty Man, The Sixth Gun, etc.) to talk 1995's neo-noir supernatural horror film "Lord of Illusions" written and directed by Clive Barker. They discuss what makes Nix such a good horror villain, Bakula's performance as Harry D'Amour, and the amazing opening sequence with the cult. They also get into the world of stage magicians vs actual magicians, Barker's history with the D'Amour character, and trope inversion of a villain trying to achieve godhood. Aaron and Derek know flesh is a trap, and magic sets them free. Cullen wanted to be a god... then changed his mind. Cullen Bunn can be found on Bluesky bsky.app/profile/cullenbunn.bsky.social Facebook www.facebook.com/cullenbunn Twitter @cullenbunn The Cullenoscopy Podcast on Youtube youtube.com/@TheCullenoscopy Links for all of his work can be found here: https://linktr.ee/cullenbunn ONLY $5 A MONTH to join our Patreon: www.patreon.com/WatchIfYouDare We are on PodBean, Apple Podcasts, Podchaser, Goodpods, Amazon Music, Spotify, iHeartRadio and CastBox. Please rate, review, subscribe, and share our show. Also, check out our Spotify Music playlist, links on our Twitter and Podbean page. Our socials are on Bluesky and Facebook and Twitter @WatchIfYouDare

In hour 3 of The Drive, Zach and Phil continue to breakdown the Broncos trade for Jaylen Waddle today. Does the addition of Waddle add pressure to Davis Webb to have this Broncos offense humming as the play caller? Will Bo Nix take a big step forward with Waddle and have Nix as a 4,000-yard passer in 2026? We react to ESPN's Mel Kiper Jr's latest mock draft and what he expects the teams in the AFC west to do. Which Broncos will be the most impacted by the addition of Jaylen Waddle, both positively and negatively? How will other teams go about defending both Waddle and Courtland Sutton on the field at the same time? Could the Broncos trade Marvin Mims or Troy Franklin to recoup draft assets with a loaded wide receiver room? We preview tonight's Nuggets and Sixers game and discuss how Jamal Murray will bounce back after playing one of his worst games of his career. 

After experiencing Planet Nix and SCaLE, we come back convinced the next phase of Linux is already taking shape.Sponsored By:Jupiter Party Annual Membership: Put your support on automatic with our annual plan, and get one month of membership for free! Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love. Support LINUX UnpluggedLinks:

Hour 1 of The Drive kicks off with Phil and Will Petersen cross talking with Dover and Cecil. The guys discuss the progress the Rockies have made this offseason and the backup quarterback situation with the Broncos. Phil and Will react to the Avalanche rolling as they beat Anaheim 5-1 last night in California. We speculate on what trade deadline deals the Avs could make and debate if it makes sense for them to bring back a familiar face in Kadri. We react to a report about the Broncos listening to offers on backup quarterback Jarrett Stidham. How much would it take in assets to move on from Stidham? Will makes the case why there are better backup quarterbacks on the market that could help the Broncos win important games if Nix were to miss any time. How close is Aaron Gordon to returning to the Nuggets lineup? Should the Nuggets hold back Gordon and Peyton Watson to make sure they are healthy for a playoff run? 

The Surveyors and their crew find themselves at a house party for Yarrow's Eve. Can they find Nix, what can the learn about the city, and (most importantly) who's taking the main stage?

Planet Nix and SCaLE are just days away, and we're getting a head start with two guests, the tech, and the trends shaping open source. Our trip starts here!Sponsored By:Jupiter Party Annual Membership: Put your support on automatic with our annual plan, and get one month of membership for free! Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love. Support LINUX UnpluggedLinks: