Podcasts about Helios

This Week In Startups is made possible by:Northwest Registered Agent - NorthwestRegistereAagent.com/TWISTEvery - Every.ioSentry - Sentry.io/TWISTToday's show:Want to get to space? Several launch companies can help you. SpaceX, Rocket Lab, the Russians, the list goes on. But what about once you make it upstairs, then what? Impulse Space CEO and CTO Tom Mueller is building the next stage of our orbital economy. With its Mira and Helios spacecraft, we'll soon be able to take mass from lower orbits to higher orbits, or even to the Moon, with ease.Meanwhile, venture capitalists are enamored with the idea of humanoid robots — robots share our shape, our work environment, and even our tools. But startups like Dusty Robotics are taking a different tack; instead of building human-shaped robots, Dusty has built a small, wheeled 'bot that can mark out building sites quickly and accurately. And it's doing more revenue than all humanoid robotics companies combined, I reckon. Dusty's CEO, Dr. Tessa Lau, joins Alex to go deep on purpose-built robots in today's build-crazy market.Timestamps:0:00 Blue Origin, and why fixing things in orbit is hard2:19 What Mira is and what it does4:35 Why was the commercial demand for Mira softer than expected5:20 Space Force demand and the GEO-capable Mira7:08 Helios: a "rocket on top of a rocket."10:10 Sentry - Your team should be focused on shipping features — not chasing down bugs. New users can get $240 in free credits when they go to https://sentry.io/twist and use the code TWIST11:35 How Helios beats Falcon Heavy on price ($25M)13:35 Reusability, in-orbit refueling, and propellant depots15:38 Landers, the Moon base, and "Mega Helios."18:52 NSSL and the politics of flying government payloads20:16 Every.io - For all of your incorporation, banking, payroll, benefits, accounting, taxes or other back-office administration needs, visit https://every.io20:51 Why the Moon matters: megastructures and data centers in space25:09 The space talent market and the SpaceX "mafia."30:16 Northwest Registered Agent: Get more when you start your business with Northwest. In 10 clicks and 10 minutes, you can form your company and walk away with a real business identity — Learn more at https://northwestregisteredagent.com/twistSubscribe to the TWiST500 newsletter: https://ticker.thisweekinstartups.comCheck out the TWIST500: https://www.twist500.comSubscribe to This Week in Startups on Apple: https://rb.gy/v19fcpFollow Lon:X: https://x.com/lonsFollow Alex:X: https://x.com/alexLinkedIn: ⁠https://www.linkedin.com/in/alexwilhelmFollow Jason:X: https://twitter.com/JasonLinkedIn: https://www.linkedin.com/in/jasoncalacanisThank you to our partners:Check out all our partner offers: https://partners.launch.co/Great TWIST interviews: Will Guidara, Eoghan McCabe, Steve Huffman, Brian Chesky, Bob Moesta, Aaron Levie, Sophia Amoruso, Reid Hoffman, Frank Slootman, Billy McFarlandCheck out Jason's suite of newsletters: https://substack.com/@calacanisFollow TWiST:Twitter: https://twitter.com/TWiStartupsYouTube: https://www.youtube.com/thisweekinInstagram: https://www.instagram.com/thisweekinstartupsTikTok: https://www.tiktok.com/@thisweekinstartupsSubstack: https://twistartups.substack.com

For many Arizona students, the path into science begins with a single summer that reshapes their confidence and their future. Since 2007, the Helios Scholars Program at TGen has been that turning point. Each year, Helios Scholars spend eight weeks working directly with TGen researchers exploring cancer biology, neurological and infectious disease, diabetes, and the fast‑growing world of computational genomics. Some even step into administrative roles that keep scientific projects moving. The program began with a Helios Education Foundation grant in 2006. The pilot's success led to a $6.5 million endowment and the official launch of Helios Scholars at TGen, a program built to educate, inspire, and strengthen Arizona's STEM workforce. Now entering its 20th year, the impact is undeniable. Alumni have published research, earned national recognition, and joined top graduate and medical programs across the country. Helios alumna Saahithi Mallapragada joins TGen Talks to discuss how her Helios experience became a launchpad for her career in science. You'll hear about her internship experience, her work in the lab, and why she would encourage anyone to apply to the Helios Scholar program to see if science might be a true passion.

Hey Bobs! We just tore through For All Mankind Season 5, Episode 9 – “Sons and Daughters,” and man… it was a gut-punch from start to finish.Donnie gave it an 8.5, Brian a solid 9. This one was all about the next generation — Alex, Lily, Avery, and Big Neck — as the Marines rolled into Happy Valley and things got brutally real. One-sided chaos, shocking losses, Alex stepping up in the tunnels, and that final standoff at Helios? Chef's kiss setup for the finale.We break down the gritty invasion, Avery's heavy moments, Palmer's wild ride, the Titan side quest, and why this felt like peak next-gen FAM storytelling. Plus: listener mail, our biggest nitpicks, and why we're beyond hyped for next week's season finale.Drop your thoughts at happyvalleyfam@gmail.com — we read every single one!See you next week, Bobs!

Patrick Moorhead and Daniel Newman return from Dell Technologies World to unpack Google I/O's Gemini-as-operating-system moment, the Blackstone-Google TPU joint venture nobody saw coming, NVIDIA's $81.6 billion quarter with a $91 billion guide, and debate whether or not the "SaaSpocalypse" is finally over. The handpicked topics for this week are: Google I/O 2026: Gemini Becomes the Operating System. Google I/O repositioned Gemini from a product to the operating layer for everything Google does, and the numbers backed it up. 900 million monthly active users, 3.2 quadrillion tokens per month, a 7x jump year over year. Pat's headline: this is about widening distribution, not just model quality. Gemini 3.5 Flash, Antigravity 2.0, Gemini Spark, and Android XR glasses all extend Gemini into surfaces that no competitor can replicate. Daniel's read: the token-cost reckoning is coming, and when enterprise subsidies end, models that can deliver value at a lower cost per token will become the ground zero of the next era. (The Decode) Dell Technologies World 2026: AI Factory Goes Agentic, 1,000 New AI Server Clients. Pat and Dan were both on the ground in Las Vegas and called it the most consequential Dell event in years. Michael Dell and Jensen Huang co-keynoted to launch the next-generation Dell AI Factory with liquid-cooled PowerEdge XE9780 servers, Dell Deskside Agentic AI, and a multi-model ecosystem including Google Distributed Cloud with Gemini 3.0, on-prem OpenAI Codex, and Grok. 1,000 new AI server clients in a single quarter is the cleanest leading indicator of enterprise demand heading into Dell's Q1 print. Pat's biggest takeaway: OpenShell as a control plane for agents spanning from the GB10 all the way to the PowerEdge rack has been the missing orchestration piece. Daniel's read: large enterprises are going to build hybrid AI architectures and want to deliver tokens at the lowest possible on-prem cost, and Dell is ready. (The Decode) Blackstone and Google Launch a $5B TPU Joint Venture. Pat called it the biggest story of the week and the one that went most under the radar. For the first time, a hyperscaler has released its proprietary AI silicon to a third-party distribution entity. The $5 billion deal, up to $25 billion with leverage, targets 500 megawatts of capacity online by 2027. Daniel's framing: Google decided its custom silicon is worth more as a commercially distributed asset than as a captive moat. Pat's note: the proprietary nature of TPU infrastructure means retrofitting existing data centers will require real work, but the sovereign angle gives the JV a natural first market. (The Decode) AMD Helios, $10B Taiwan Investment, and the MI450 Anchor Customer Rumor. AMD dropped a $10 billion Taiwan ecosystem investment alongside confirmation that Helios rack-scale is on track for multi-gigawatt customer deployments beginning 2H 2026. A Citi rumor surfaced Anthropic as the anchor MI450 customer, to be formally announced at AMD's Advancing AI Day in July. Pat's read: Lisa Su has made a commitment and she almost never falls through. The analysts who said AMD would not ship anything in the second half of 2026 are going to be very wrong. (The Decode) OpenAI Guaranteed Capacity: Sam Altman's Moment. OpenAI launched multi-year compute commitment contracts the same week that Anthropic was struggling with capacity outages. Pat called it brilliant and said it makes Sam Altman look like a genius. It's the inference-era analog of cloud reserved instances: guaranteed availability at a locked price for one, two, or three years. Daniel added context: Anthropic's annualized ARR growth is nearly double OpenAI's and is about to lap them, so the model war is far from over. But for enterprises that need reliability, OpenAI just made the most compelling enterprise trust argument of the week. (The Decode) Sovereign AI Crosses $30 Billion at NVIDIA, 14% of Revenue. NVIDIA disclosed sovereign AI as a segment-level line for the first time, at $30 billion in FY26, 3x the prior year. Pat has been tracking sovereign for years and calls this the clearest possible signal that it has moved from marketing term to structural revenue category. Daniel's point: outside of the four or five hyperscalers doing all the major buying, sovereign is where the incremental demand is coming from and it is very real. (The Decode)  The Flip: Is the SaaSpocalypse Over? Daniel took the affirmative and came in loaded. Every earnings report across CrowdStrike, Cloudflare, ServiceNow, Intuit, Salesforce, Atlassian, Notion, and monday.com shows companies growing with the AI tailwind. His core argument: there was a reason SaaS emerged 20 to 30 years ago. Companies do not want to be in the software business. Vibe-coded flat-file apps with no security, no governance, no data lineage look great in a kitchen demo and fall apart at enterprise scale. The SaaSpocalypse is over and he is tired of talking about it. Pat's counter: BofA slapped Salesforce with an Underperform at $160, 8% below where it trades. Snowflake is down 35% year-to-date. A senior Dell executive told him Dell will not buy another SaaS system and is tripling internal software creation. The growth question is real even if the terminal value is not zero. Both agree the tape will tell the real story. (The Flip) NVIDIA Q1 FY27 Results. Record $81.6 billion revenue, up 85% year over year. Data center at $75.2 billion, up 92%. Non-GAAP EPS of $1.87, up 140%. Q2 guide of $91 billion crushed the $86.8 billion consensus by $4 billion at the midpoint. $80 billion buyback authorized, dividend raised 25x. The stock went down after hours for the fifth consecutive time following a massive beat and raise. Pat's read: NVIDIA may be worth $8 to $9 trillion on paper at a sector-average multiple and 75% gross margins held. Daniel's framing: this is the best company in the world, possibly tied with Google, and it is becoming the Apple of this era. He sees a long safe journey of continued growth vs. speculative dollars chasing quantum and space names that can double in a week. (Bulls and Bears) Intuit: Earnings Beat, Revenue Miss. A 17% workforce cut, raised guidance, and $8 billion buyback were authorized. Pat's emerging thesis: these companies are cutting people to afford tokens. Intuit comes at a moment when OpenAI's ChatGPT finance plugin via Stripe is building an intelligence layer that could sit on top of Intuit's products without displacing them directly, at least not yet. (Bulls and Bears) Lenovo: Record $21.6 billion quarterly revenue, up 27% year over year. The company's fastest growth in five years. AI-related revenue is up 84% year over year to 38% of total company revenue. ISG returned to full-year operating profit with a $21 billion AI server pipeline. Pat and Dan both read Lenovo's results as NVIDIA tea leaves, a leading indicator of enterprise AI server demand that directly validates what Dell said on stage about 1,000 new AI server clients. (Bulls and Bears) Analog Devices: Record $3.62 billion revenue, up 37% year over year. EPS up 67%. Q3 guide of $3.9 billion crushed consensus by $270 million. Data center up 90%, industrial up 56%, comms up 79%. The $1.5 billion Empower Semiconductor acquisition adds integrated voltage regulator technology that can reduce AI data center power consumption by 10 to 15% while shrinking the power footprint by up to 4x. Daniel's closing point: you can't build AI servers without players like Analog Devices and Lattice Semiconductor. These essential node companies aren't boring, they're foundational. (Bulls and Bears) Check out all of our Dell Technologies World coverage linked in the show notes including our sit-downs with Michael Dell, Jeff Clark, and key customers. Be part of our community. Hit that subscribe button and see you at Computex.   The Decode Google I/O 2026 — Gemini Becomes the Operating System: 900M MAU, 3.2 Quadrillion Tokens/Month, Gemini Omni, Antigravity 2.0, Gemini Spark, and Android XR Glasses https://blog.google/innovation-and-ai/sundar-pichai-io-2026/ Dell Technologies World 2026 — AI Factory Goes Agentic: Michael Dell + Jensen Huang Unveil PowerEdge XE9780, Dell Deskside Agentic AI, and a Multi-Model Ecosystem; Dell Adds 1,000 AI-Server Clients in the Quarter https://www.dell.com/en-us/blog/dell-technologies-world-a-bright-and-beautiful-road-ahead/ Blackstone + Google Launch $5B (Up to $25B w/ Leverage) JV to Sell Google TPUs Outside Google Cloud — First Time a Hyperscaler Has Released Its Custom Silicon to a Third-Party Distribution Channel; 500 MW Online by 2027, Benjamin Treynor Sloss as CEO https://www.blackstone.com/news/press/blackstone-announces-joint-venture-with-google-to-create-new-tpu-cloud/ AMD Announces $10B+ Taiwan Ecosystem Investment — Helios Rack-Scale Platform With MI450X GPUs and Venice EPYC on TSMC 2nm Targeting Multi-Gigawatt Deployments 2H 2026; the Clearest Second-Source Signal Yet https://ir.amd.com/news-events/press-releases/detail/1286/amd-announces-more-than-10-billion-in-taiwan-ecosystem-investments-to-accelerate-ai-infrastructure OpenAI Launches Guaranteed Capacity — Multi-Year Compute Commitments Turn Inference Capacity Into a New Enterprise Asset Class https://www.cnbc.com/2026/05/19/openai-announces-new-guaranteed-capacity-offering-for-customers-to-secure-compute.html The Sovereign AI Government Investment Wave — NVIDIA Discloses ~$30B Sovereign-AI Revenue (14% of Mix); UAE, Saudi, Japan, Australia, France All in Motion This Week https://finance.yahoo.com/markets/stocks/articles/analog-devices-q2-earnings-beat-153000996.html   The Flip: Is the SaaSpocalypse Officially Over — or Is BofA's Split Call (ServiceNow Buy, Salesforce Underperform) the Real Signal That Platform AI Monetization Is Going to Be Bifurcated, Not Universal? FOR:  BofA Reinstates Coverage of ServiceNow, Salesforce — Barron's (May 18) https://www.barrons.com/articles/servicenow-salesforce-stock-price-ai-7b109396 Embedded workflow + system-of-record stickiness still wins citing ServiceNow Q1 2026 financial results https://newsroom.servicenow.com/press-releases/details/2026/ServiceNow-Reports-First-Quarter-2026-Financial-Results/default.aspx Intuit Q3 revenue up 10%, cuts 17% of staff — SEC 8-K filing (May 20) https://www.stocktitan.net/sec-filings/INTU/8-k-intuit-inc-reports-material-event-b23073259896.html   AGAINST:  BofA Slaps Salesforce With Underperform Rating, $160 Price Target — 24/7 Wall St (May 18) https://247wallst.com/investing/2026/05/18/bofa-slaps-salesforce-with-underperform-rating-160-price-target-is-the-ai-story-falling-flat/ BofA resets Salesforce price target to Underperform — TheStreet (May 19) https://www.thestreet.com/investing/stocks/bofa-resets-salesforce-stock-price-target-to-underperform-at-160 Snowflake -35% YTD heading into May 27 print is the canary that platform stickiness is being repriced https://eciks.org/4640-22295-snowflake-set-to-report-q1-earnings-may-27-with-ai-strategy-in-focus OpenAI Guaranteed Capacity + Dell on-prem Codex create a credible path to displace seat-based SaaS https://www.cnbc.com/2026/05/19/openai-announces-new-guaranteed-capacity-offering-for-customers-to-secure-compute.html Bulls & Bears NVIDIA Q1 FY27 ACTUALS https://www.cnbc.com/2026/05/20/nvidia-nvda-earnings-report-q1-2027.html Intuit Q3 FY26 Actuals https://investors.intuit.com/news-events/press-releases/detail/1312/intuit-reports-strong-third-quarter-results-and-raises-full-year-revenue-guidance Lenovo Q4 FY26 ACTUALS https://www.cnbc.com/2026/05/22/lenovo-shares-jump-15percent-on-record-earnings-as-ai-revenue-nearly-doubles.html Analog Devices Q2 FY26 ACTUALS https://finance.yahoo.com/markets/stocks/articles/analog-devices-q2-earnings-beat-153000996.html  

Today we're doing a throwback episode to one of our favorites from the early days of Stories Podcast. Phaeton Steals the Sun! Demigod Phaeton wants to be JUST like his father, Helios, the god of the sun, but he doesn't want to wait until he's a grown up! What will happen when he tries to drive the sun chariot without permission? Listen in to this adaptation of the Greek myth to find out! Check out Stories RPG our new show where we play games like Starsworn with all your Max Goodname friends, and Gigacity Guardians featuring the brilliant firefly! https://link.chtbl.com/gigacity Draw us a picture of what you think any of the characters in this story look like, and then tag us in it on instagram @storiespodcast! We'd love to see your artwork and share it on our feed!! If you would like to support Stories Podcast, you can subscribe and give us a five star review on iTunes, check out our merch at storiespodcast.com/shop, follow us on Instagram @storiespodcast, or just tell your friends about us! Check out our new YouTube channel at youtube.com/storiespodcast. If you've ever wanted to read along with our stories, now you can! These read-along versions of our stories are great for early readers trying to improve their skills or even adults learning English for the first time. Check it out.

Podcast presentado por Toni Asensio y producido por Radioesport valencia en colaboracion con la Federació de Futbol de la Comunitat Valenciana.

M

Hey Bobs! We're talking For All Mankind Season 5, Episode 5 – “Svoboda” (freedom, baby).Donnie landed on a 6.5 while Brian gave it a solid 8. This one had an absolute banger of a cold open with Irena Morozova, some heavy political fallout from the automation leak, Alex and Dev's complicated dynamic, and a tense standoff in Happy Valley that ends in chaos.We break down the corporate espionage vibes between Helios and Kuragin, Boyd connecting more dots, Miles having to pick a side, and that powerful closing sequence. Plus: listener mail, why the governor's still the worst, and why we're pumped for whatever's coming next.Drop your thoughts at happyvalleyfam@gmail.com — we read every one!See you next week, Bobs!

Die Folge wird unterstützt von SCHELL, SANHA, Dallmer, ELYSATOR, ADEY und Helios Ventilatoren. Die IFH/Intherm 2026 in Nürnberg hat im Jubiläumsjahr einmal mehr gezeigt, warum sie seit 50 Jahren als zentraler Treffpunkt der SHK-Branche gilt. Mit rund 38.000 Besuchern und über 400 Ausstellern bot die Messe einen umfassenden Überblick über aktuelle Trends, Technologien und Herausforderungen – von Digitalisierung über Trinkwasserhygiene bis hin zur Wärmewende. Genau diese Themen greifen wir in dieser Podcastfolge mit dem rollenden Podcaststudio auf. - Moderator Max Herrmannsdörfer spricht mit Benjamin Kraus, Leiter Produktmanagement bei SCHELL, über die digitale Armaturengeneration E², den SCHELLTRONIC E² und die Möglichkeiten smarter, appgesteuerter Sanitärtechnik. (03:13 – 09:30) - Mit Sven Kalbitzer, Teamleiter PR & Marketing bei SANHA, geht es um bleifreie Legierungen für Trinkwasser-Fittings, regulatorische Anforderungen und die neue Serie ACR Copper Press für Kälte- und Klimaanwendungen. (09:32 – 15:58) - Aloys Koch, Gesamtvertriebsleiter bei Dallmer, spricht über neue Normen in der Entwässerungstechnik, das weiterentwickelte System DallFlex 2.0 und sogenannte „Hidden Champions“, die auf der Baustelle den Unterschied machen. (15:59 – 22:40) - Außerdem im Gespräch: Tino Sarro, Geschäftsführer der ELYSATOR Engineering GmbH, und Konstantin Papadopoulos, Sales Director DACH bei ADEY. Thema ist die neue Kooperation beider Unternehmen sowie aktuelle Produktlösungen wie der MagnaClean HP Wärmepumpenfilter und der H2O Desal Messzähler zur digitalen Wasseranalyse. (22:41 – 30:08) - Zum Abschluss: Thorsten Fiedel, Leiter Schulungswesen bei Helios Ventilatoren, gibt Einblicke in die Kampagne „Upgrade Air“ und das dezentrale Lüftungsgerät KWL EC 70 mit Zweitraumanschluss für flexible Einsatzbereiche. (30:09 – 36:30) Mehr Infos: https://www.schell.eu www.sanha.com https://www.dallmer.de/de/ https://elysator.de/ https://adey.com/eu/de/ https://www.heliosventilatoren.de/de/

The Live Long and Podcast crew continues their journey through Season 5 of For All Mankind with Episode 4, "Open Source" (2026). A memorial for Ed, a mission to Titan, and a leak that could destroy Helios.For All Mankind S5 E4 – "Open Source" (2026) Episode ReviewFirst Aired: April 17, 2026In-universe year: 2012Date of Podcast: April 20, 2026For All Mankind Review SeriesTHIS WEEK'S PODCASTERSDave Mader, Adam Woodward, Jody Simpson, Heather Narduzzi, Jeff MaderLIVE LONG AND PODCAST FOUNDED BYDave Mader and Jaemeel RobinsonA PROUD MEMBER OF THE UNITED FEDERATION OF PODCASTSCheck us out online at https://www.ufpodcasts.com/livelongandpodcastPRODUCERDave MaderSupport us on Patreon at https://www.patreon.com/LiveLongandPodcastStreaming live on Twitch, Youtube and Facebook:Twitch Channel: https://www.twitch.tv/livelongandpodcastYouTube Channel: https://www.youtube.com/user/livelongandpodcastFacebook Page: https://www.facebook.com/pg/LiveLongAndPodcastThe Moment of Triumph by MaxKoMusic | https://maxkomusic.com/Music promoted by https://www.chosic.com/free-music/all/Creative Commons CC BY-SA 3.0https://creativecommons.org/licenses/by-sa/3.0/Audio version available wherever you get your audio podcasts.Listen to Spotify: https://open.spotify.com/show/0yIEMJhawSLGAozJAh4EdGListen via Anchor: https://anchor.fm/livelongandpodcast#forallmankind #startrek #livelongandpodcast #UFP #unitedfederationofpodcasts 0:00 Intro Credit Sequence1:41 Beginning of Podcast14:17 Screenshots and Plotbreakdown1:06:22 Fun Facts1:16:15 Ratings1:18:20 Outro

Hélios fête ses 10ans !!Dix ans ça se fête, pour l'occasion on a rencontré le président et DJ de l'association, Victor Garbaccio ! Dans cet épisode, on replonge dans les débuts de l'asso, les souvenirs précieux et tout ce qui fait d'Hélios ce qu'elle est aujourd'hui. Ce n'est pas tout...Hélios vous donne rendez-vous le 25 avril au théâtre le Normandy, une institution havraise... Au programme Oden & Fatzo ainsi que Herr Krank artistes locaux et dorénaant à la renommée mondiale !On vous attend nombreux.ses pour célébrer comme il se doit les 10ans d'Helios au théâtre Le Normandy, réservations sur le site

The Acer Predator Helios Neo 14 AI is here, and it's redefining what a compact gaming laptop can do. In this review, I break down everything you need to know about this 14-inch powerhouse featuring an Intel Core Ultra 9 processor, NVIDIA RTX 5060 GPU, and a stunning 2.8K OLED display.From real-world gaming performance to thermals, AI-powered features, and whether this can truly replace a full gaming setup… we're putting it all to the test.Is this the best portable gaming laptop of 2026? Let's find out.

Hey Bobs! We're back with our take on For All Mankind Season 5, Episode 4 – “Open Source.”Donnie and Brian both landed on a solid 8/10 for this one. It felt like a proper middle-of-the-season bridge episode with good forward momentum: Alex starts his Helios gig (and immediately finds trouble), Alida arrives on Mars and teams up with Kelly, we finally meet Avery Stevens (Danny's daughter), and that big automation leak drops like a bomb on Happy Valley.We break down the Dev/Alex dynamic, the Sojourner T launch, Dani's surprise cameo, Irina Morazova's arrival, and why every scene with the governor still makes us groan. Plus: listener mail from Jade and Brad, why the show feels like it's back on track, and some classic nerd tangents about Apple mice and scale on Mars.Drop your thoughts at happyvalleyfam@gmail.com — we read every one!See you next week, Bobs!

Who bonked Boyd? Why do Helios and Kuragin care about finding bacteria on Titan? Who, among the original cast, remains and who, among the rest of the cast, do we care to keep following? Nique is joined by Kevin and Gus to discuss these questions and more as they review the third episode of the fifth season of AppleTV's For All Mankind.Join the conversation on Discord at the Moon Show Podcast server.

When two fighter jets came to check on the unresponsive Helios Flight 522, they were stunned at what they saw: all 115 passengers, lying motionless in their seats. Even worse – the pilot's seat was empty, and the co-pilot lay slumped over the control panel. The commercial plane was drifting along at 34,000 feet, on autopilot – and fuel was running out. This is the ShortHand.--Patreon - Ad-free & Bonus EpisodesYouTube - Full-length Video EpisodesTikTok / Instagram

This episode explores Circe in Greek mythology through Homer's Odyssey, presenting her as a powerful sorceress and full goddess born to Helios and a sea nymph, embodying balanced sun-and-moon energy. Circe is known as a powerful witch with vast knowledge of potions and herbs. On her lush, animal-filled island, she welcomes Odysseus's men to a feast laced with potions that transform them into swine as a mirror of their recent war behavior. Warned by Hermes and protected by Athena's herb, Odysseus resists Circe's magic, confronts her, and they become lovers, living together for years and having three sons; she later restores his men. Circe then teaches Odysseus necromancy—witchcraft with the dead—so he can enter the underworld, consult an expert, and learn how to navigate back to Ithaca. Circe, a powerful witch and left on her solitary island, will help you to explore power, ethics, self-knowledge, and intent in magic. If you are loving this podcast and you feel really motivated or compelled to share, please donate to this podcast: Donate here Connect with the Goddesses:  https://www.goddesswitchwomb.com  Follow us on Instagram: https://www.instagram.com/goddesswitchwomb/  Follow us on TikTok https://www.tiktok.com/@goddesswitchwomb

“Voices Across the Timeline: Conversations from Seasons 1–4” In this special edition of Rewind: On For All Mankind, we're celebrating the journey of Apple TV+'s alternate‑history epic by bringing together interview moments from across the show's first four seasons.  Whether you're revisiting the early days of the space race or reflecting on the seismic shifts of the Helios era, this episode offers a rare look at how the world of For All Mankind evolved—on screen and behind the scenes.

Ed Baldwin just pulled a prison break… on Mars.For All Mankind Season 5 Episode 2 (“The Hard Six”) takes the slow-burn premiere and hits the gas — with a daring jailbreak, a possible conspiracy on Mars, and one of the biggest discoveries in human history:

“Flight” by Jess Helios and The Crew began as a song about revolution, but grew into something more personal, tapping into inner truth and rising to a higher state of mind. It offers a glimpse into their unreleased album Apollo 95, a cinematic, genre-blending journey through grief, love, and the full spectrum of human emotion, where […] The post Jess Helios and the Crew: “Flight” appeared first on KUT & KUTX Studios -- Podcasts.

Join me as we explore the fascinating world of early season olive hatches with expert fly fisherman Blake Katchur [35:42] of Anglers All in Denver. No matter where you fish, you'll find this hatch any time from early March to early June. Discover effective tactics, fly patterns, and timing tips to enhance your fishing success during this prolific hatch. In the Fly Box this week, we have these questions and more: Can I use my 7-weight fiberglass rod for bonefish in Belize? Why can I catch brook trout in smaller streams during the winter but not in a bigger river? If I leave off the trailing hook in articulated flies, how do I compensate for the lack of weight?  Will it affect the swimming action of my flies? For Alaska silver salmon and big rainbows, should I get a 9-foot or 10-foot 8-weight Helios rod?  And should I pick Helios D or F? Do the scents from resins and glues put off the fish?  Is there anything that can cover up these scents? Are wings on dry flies absolutely necessary? Where did we get the "X" system we use for leader and tippet diameters? What do you have on your fly-tying bench that you can't do without?

Tom Mueller, Founder and CEO of Impulse Space, joins me to catch up on the company's progress and plans—3 Mira missions flown, Helios soon to fly, $525M raised, new defense contracts, a lunar lander concept, and a new Colorado facility. This episode of Main Engine Cut Off is brought to you by 33 executive producers—Joel, Tim Dodd (the Everyday Astronaut!), Warren, Steve, Ryan, Will and Lars from Agile, Natasha Tsakos, Russell, Joakim, Theo and Violet, The Astrogators at SEE, Matt, Lee, Donald, Heiko, Better Every Day Studios, Josh from Impulse, Miles O'Brien, Stealth Julian, David, Joonas, Kris, Frank, Jan, Fred, Pat, and four anonymous—and hundreds of supporters. Topics Impulse Space Careers - Impulse Space Tom Mueller (@lrocket) / X Inside Impulse's New Colorado Facility Impulse Space Secures $300 Million Series C to Accelerate the Future of In-Space Mobility Starfish Space Completes Autonomous Rendezvous and Proximity Mission in LEO with Impulse Space To the Moon (and Beyond): How Impulse Can Deliver More Mass to the Lunar Surface ​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌​​​‌‍‌‌‌‍‌‍​‌‍​‌‌​​‌​‍‌​​​​‍‌‌‍​‌‍‌‍​‍​‌‍‌​​‍‌​‌​​‌‍​​‌​‍‌​‍‌​‍​‌‍‌‌​‍​‌‍​‍​‍‌‌‍​‍‌‍‌‍​‌​​‍‌​‍​​​‍​‌‌‍​‌​​‍‌‍​‌‍‌‌​‌​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌‌‌‌​​‌‍‌​‌‍​‌‌‌​‌‍‌‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‌​‌‍​‌‍‌‌​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌​​​‌‍‌‌‌‍‌‍​‌‍​‌‌​​‌​‍‌​​​​‍‌‌‍​‌‍‌‍​‍​‌‍‌​​‍‌​‌​​‌‍​​‌​‍‌​‍‌​‍​‌‍‌‌​‍​‌‍​‍​‍‌‌‍​‍‌‍‌‍​‌​​‍‌​‍​​​‍​‌‌‍​‌​​‍‌‍​‌‍‌‌​‌​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌‌‌‌​​‌‍‌​‌‍​‌‌‌​‌‍‌‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‌​‌‍​‌‍‌‌​‍​‍‌‌ Introducing the Upgraded Mira: Bringing In-Space Mobility to GEO and Beyond The Show Like the show? Support the show on Patreon or Substack! Email your thoughts, comments, and questions to anthony@mainenginecutoff.com Follow @WeHaveMECO Follow @meco@spacey.space on Mastodon Listen to MECO Headlines Listen to Off-Nominal Join the Off-Nominal Discord Subscribe on Apple Podcasts, Overcast, Pocket Casts, Spotify, Google Play, Stitcher, TuneIn or elsewhere Subscribe to the Main Engine Cut Off Newsletter Artwork photo by NASA/John Kraus Work with me and my design and development agency: Pine Works

Benvinguts al "Generaci

On explore les avancées spectaculaires de l'intelligence artificielle, les dérives possibles des chatbots et les innovations technologiques qui pourraient transformer l'industrie. Génération vidéo, IA chinoises, deepfakes et infrastructures énergétiques : tout ce qu'il faut comprendre cette semaine dans cet épisode du podcast Tech Café.  Me soutenir sur Patreon Me retrouver sur YouTube On discute ensemble sur Discord Dans le soft Vie des hauts : Helios, Cubecomposer. En poids en en volume :  Realwonders, restauration et mouvements 3D. Pourquoi tant de Qwen ? Par tous l'essaim : Kimi K2.5. Gemini envoie un agent en mission pour le retrouver. Clueless : tricher n'est pas jouer. Combien faut-il de neurones pour jouer à Doom ? Des modèles 3D fourmidables ! Dans le dur Ca m'Iran malade : après les cyberattaques, les… attaques. Terrapower ne manque pas de sels. Aikid'eau : et maintenant, des datacenters offshores… L'optique sans la fibre, Taara le bol des fils. NVIDIA préfère l'optique avec la fibre.  Nouveaux Xeons, nouvelles mémoires. Linux, définitivement un OS de barbus. Participants Une émission préparée par Guillaume Poggiaspalla Présenté par Guillaume Vendé

We're back! Jasmine and Michelle have returned to bring you a limited series for 1313 Harbor the Podcast - the Epic Universe Saga. In our first episode, we'll discuss the fabulous Grand Helios Hotel and the main hub for Epic Universe, Celestial Park. Did we love it? (we did) But did we really love it? (spoiler: we really did). Support the show

Our Academy Award Best Picture Oscar picks: One Battle After Another, Sinners, Sentimental Value, Helios, Epic Universe

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

The next in our series of discussions with CEO's of companies that are putting AI to work has Fransico Martin-Rayo of Helios discussing the agricultural supply chain with host Eric Hanselman. Helios is leveraging AI to generate insights in the complex dynamics of food production and sourcing at a dramatically finer level of granularity. AI not only enables more complex analysis but also allows customized delivery of the results. Shifting interfaces from legacy dashboards and static reports to queryable constructs lets users explore the analyses in ways that better fit their needs. AI can deliver custom insights at scale in ways that weren't possible with traditional application interfaces. One of the principal shifts accelerating AI, is the availability of better data. Helios integrates massive weather data sets with market history and global events to generate forecasts. While the volumes of data are growing it's seen significant reductions in the cost per token in their infrastructure. Improving efficiency can expand the depth of analysis, as well as the frequency of forecast updates. More S&P Global Content: ANALYSIS: Tariff gap likely to keep China's soybean imports anchored to Brazil India to export 2.5 million mt wheat after near 4-year ban Look Forward Journal: Geopolitics of data centers Next in Tech | Ep. 209: Datacenters and Energy Markets in Europe For S&P Global Subscribers: 2026 Trends in Data, AI & Analytics 2026 US Data Centers and Energy Report Highlights from Enlit Europe 2025: Flexibility, visibility and digital energy Credits: Host/Author: Eric Hanselman Guest: Francisco Martin-Rayo, CEO and Co-Founder of Helios Producer/Editor: Feranmi Adeoshun Published With Assistance From: Sophie Carr, Kyra Smith

The crew of the AGA-0 were swarmed by Helios soldiers on Colony 9, and now find themselves inside the mysterious white light...

If you think mending is just lifting your rod and flipping it upstream—well sometimes it is—but there is so much more you can do with line mends to add slack in just the right places, and to deal with tricky currents. Mike Pease [30:41], Orvis-endorsed guide and great storyteller, gives us 10 tips for increasing the utility of your line mends. I learned a bunch of new tricks on this podcast and I am sure you will as well. There are some helpful tips from listeners and some questions that may answer things you have been curious about, including: When would you use a drop shot nymphing rig? Have you ever used a dry fly, nymph, and wet fly at the same time? I am debating about which Helios rod to buy. Should I get the 9 foot 5 weight or the 9-foot 5-inch version?  Can I use the longer rod for wade fishing? A listener gives his version of a Euro rig for steelhead. Which 10-foot rod should I get for Lake Erie steelhead? Do you think tying a dropper to the bend of a hook is any hindrance to fish taking the upper fly? Sometimes when I hook a big fish it takes line right away and my tippet breaks. Do you think my drag is set too tight?  How tight should I set my drag? A great tip from a listener on an easy way to remove split shot with a tool everyone carries. You say that trout can always see the tippet. If so, why would I ever want to use something as fine as 6X? 

You can't scale AI on fragmented data. In this episode of Technovation, Peter High speaks with Ogi Redzic, Chief Digital Officer of Caterpillar, about the foundational platform transformation that made rapid AI innovation possible across a $65B industrial enterprise. Ogi shares how retiring legacy systems, consolidating data into the Helios cloud platform, and establishing trusted data pipelines enabled CAT Digital to launch an enterprise AI assistant in just 10 months. Key topics include: Building Helios to process millions of data pipelines daily Turning unplanned downtime into predictive maintenance at scale Scaling $5B in industrial e-commerce Partnering with NVIDIA on edge AI and digital twins Aligning digital teams to measurable business outcomes

Watch Here : https://www.youtube.com/watch?v=iWP047x7w2g Website: https://vigoroussteve.com/ Consultations: https://vigoroussteve.com/consultations/ eBooks: https://vigoroussteve.com/shop/ YouTube Channel: http://www.youtube.com/user/VigorousSteve/ Workout Clips Channel: https://www.youtube.com/channel/UCWi2zZJwmQ6Mqg92FW2JbiA Instagram: https://instagram.com/vigoroussteve/ TikTok: https://www.tiktok.com/@vigoroussteve Reddit: https://www.reddit.com/r/VigorousSteve/ PodBean: https://vigoroussteve.podbean.com/ Spotify: https://open.spotify.com/show/2wR0XWY00qLq9K7tlvJ000 Patreon: https://www.patreon.com/vigoroussteve

My guest this week is philosophy professor and fly fisher Thi Nguyen [33:31], who has spent his career studying the psychology and the value of games to our mental well-being. He argues that fly fishing is not one game but an infinite number of games that can be played by rules that we invent to challenge ourselves. And you might even change your rules within a single day of fishing. This podcast and my discussions with him have changed the way I view and teach fly fishing and I hope the interview will be equally fascinating to you. The Fly Box this week has some interesting tips and questions. Perhaps not as thought-provoking but still interesting, and I hope helpful. Will a premium rod magnify my casting mistakes? Will my 4-weight Helios handle brown trout over 20 inches? Can you elaborate on why someone would want to use two indicators and how to set them up? Will my nymphs sink better with 12-pound fluorocarbon or with lighter tippet? I am confused by the differences in hook sizes recommended for various diameters of beads. They don't seem consistent. Can you help? A tip for using paper key tags to learn to identify various flies A tip for using parachute cord to eliminate the loss of small items Why do I see bugs under rocks in one part of a river and not in another?

How does a 100-year-old manufacturing leader reinvent itself through autonomy and AI? In this episode, Caterpillar CTO Jaime Mineart shares how her team is transforming industrial work sites using robotics, machine intelligence, and real-time data. From mining to construction, the company is applying decades of engineering expertise to modern digital challenges, partnering with customers to co-develop scalable automation solutions. Key highlights from the episode: How autonomy is expanding beyond mining into quarries and construction What makes Caterpillar's AI adoption strategy unique—and replicable Inside the Helios platform and NVIDIA partnership powering data-driven insights Why the company pledged $100M to upskill the workforce of the future Lessons from scaling R&D with real-world customer involvement

Episode Description: The day starts with Max trying to score goals on the soccer field – but ends with the Problem Solvers trying to meet their goal of finding the next server.  This takes them back to Ancient Greece and the legendary Colossus of Rhodes statue.   There the foursome of Max, Molly, Katrina and Charlene use unit conversions, time calculations, and problem-solving to outsmart history without changing it. But when a shadowy figure appears, they realize the POGs may be closer than ever. Math Concepts: Circumference and diameter of a circle; Using π (Pi) to calculate diameter from circumference; Unit conversion (feet to inches, cubits to inches/feet); Area comparison using real-world objects (soccer balls vs. goal size); Multiplication strategies (mental math using ×11); Time calculationsHistory/Geography Concepts:  The Colossus of Rhodes and the Seven Wonders of the Ancient World; Ancient Greece (Rhodes, 230 BCE); The Siege of Rhodes; Ancient measurement systems (cubits); Greek mythology (Helios, Oracle of Delphi)

In this episode, I was lucky enough to interview Bill Near, Founder and CEO of Helios, a performance wearable helping hockey players and teams improve faster through motion-based data and video integration. Bill breaks down Helios' first-principles approach to avoiding “tech fatigue” by delivering recurring, practical value—most notably through time-saving video workflows and emerging AI-driven coaching insights that turn raw data into actionable development guidance for players and parents alike.Bill also shares the personal and technical journey behind Helios, from growing up playing hockey in New Hampshire to studying engineering at MIT and recognizing a critical gap in player development technology. He explains how Helios was built as a zero-infrastructure solution using motion sensors rather than rink-based tracking, enabling scalable adoption across youth, collegiate, and professional levels. Be inspired by Bill Near's clear-eyed take on data, coaching, and building technology athletes actually stick with on in this episode of The First Customer!Guest Info:Helioshttps://helioshockey.com/Bill Near's LinkedInhttps://www.linkedin.com/in/billnear/Connect with Jay on LinkedInhttps://www.linkedin.com/in/jayaigner/The First Customer Youtube Channelhttps://www.youtube.com/@thefirstcustomerpodcastThe First Customer podcast websitehttps://www.firstcustomerpodcast.comFollow The First Customer on LinkedInhttp://www.linkedin.com/company/the-first-customer-podcast/

In this episode of Book Talk for BookTok, we sit down with T.C. Kraven, author of Of Prophecies and Pomegranates, a dark mythological retelling that grapples honestly with one of the most contested stories in Greek mythology: Hades and Persephone. Together, we explore how Kraven approached retelling a myth that has been romanticized, sanitized, and rewritten countless times. We discuss what it means to engage with the original mythos, including the complicated history behind the so-called “Rape of Persephone,” and how linguistic nuance, power, and consent shaped her interpretation of Persephone's story. This conversation also dives into one of the novel's central thematic threads: self-deception. From Demeter's possessive motherhood, to Helios's obsession, to Hades's self-punishment, we unpack how characters lie to themselves in the name of love, protection, and control. We pay special attention to Kraven's striking portrayal of Demeter as an abusive parent and why that interpretation felt both mythologically grounded and narratively necessary. We also talk about Narcissus, whose arc moves beyond vanity into something far more human and tragic, and why his emotional depth matters to the story as a whole. Finally, for aspiring writers, Kraven shares candid insight into her journey through self-publishing and her transition into traditional publishing, offering thoughtful advice for authors navigating both paths. This episode is a must-listen for readers interested in mythological retellings, feminist reinterpretations of Greek myths, and stories that refuse to look away from uncomfortable truths. Find T.C Kraven Her Website: https://tc-kraven.square.site/ Instagram: t.c.kravenauthor TikTok: oracleoforleans Trigger Warning: This episode includes discussion of sexual assault, sexual harassment, and non-consensual behavior. Listener discretion is advised. How to participate: Send your theories and spicy takes by commenting on this episode, DMing us, or using the form on our website. The Subtext Society Journal: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://thesubtextsocietyjournal.substack.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  We're thrilled to announce our newest venture: The Subtext Society Journal—the first of its kind, dedicated to Romance, Romantasy, and fandom with an academic yet accessible voice. We're publishing original essays and thought pieces, and we encourage listeners to submit their own articles for a chance to be featured. Sponsor: Monarch Use code BOOKTALK at Monarch.com for 50% your first year. Sponsor: Liquid IV Liquid I.V. Go to LiquidIV.com and get 20% off your first order with code BOOKTALK at checkout. Sponsor: Vionic Use code BOOKTALK at checkout for 15% off your entire order at www.vionicshoes.com when you log into your account. 1 time use only. Share your thoughts for a chance to be featured! Submit them at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠booktalkforbooktok.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ for a future mini-episode or exclusive Patreon discussion. Support the Show:  Patreon: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠patreon.com/booktalkforbooktok⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  Merch: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Etsy Store⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Follow Us on Social: Instagram: @BookTalkForBookTok TikTok: @BookTalkForBookTok YouTube: @BookTalkForBookTok Learn more about your ad choices. Visit megaphone.fm/adchoices

Nous sommes au tournant du dernier siècle avant JC. Strabon, géographe et historien grec né à Amasée dans le royaume du Pont, (aujourd'hui une région appartenant à la Turquie), écrit à propos de l'antique cité de Rhodes : « J'ajouterai qu'on ne peut admirer assez l'excellence de ses lois et le soin qu'elle a toujours apporté aux diverses branches de l'administration et à la marine en particulier, ce qui lui a assuré pendant longtemps l'empire de la mer et donné les moyens de détruire la piraterie et de mériter ainsi l'alliance du peuple romain et de ses amis les rois grecs d'Asie. Or, grâce à ces alliés, elle a pu maintenir son indépendance, en même temps qu'elle se voyait décorer par eux d'une foule de monuments ou d'objets d'art, dont la plus grande partie est aujourd'hui dans le Dionysium et dans le Gymnase, tandis que le reste est dispersé dans les différents quartiers de la ville. De tous ces monuments, le plus remarquable est sans contradiction la statue colossale du Soleil, œuvre de Charès de Lindos, comme nous l'apprend l'ïambographe (le poète) auteur de l'inscription : « De sept fois dix coudées Charès de Lindos l'a faite ». Par malheur le colosse gît maintenant étendu sur le sol ; renversé par un tremblement de terre, il s'est brisé en tombant à partir des genoux, et les Rhodiens, pour obéir à je ne sais quel oracle, ne l'ont point relevé. » Géant de bronze dressé face à la mer Égée, le Colosse de Rhodes dominait l'entrée du port comme un défi lancé aux ennemis et au temps. Monumental hommage au dieu Hélios, il n'a existé qu'un peu plus d'un demi siècle mais est devenu l'une des légendes les plus durables de l'Antiquité. Aujourd'hui encore, son ombre, pourtant imaginaire, continue de fasciner, symbole d'audace et de démesure. Tentons d'en percer les mystères … Avec nous Sébastien Polet, historien-orientaliste, de l'asbl Roma. sujets traités : colosse, Rhodes,Strabon, empire, Gymnase, Charès de Lindos,Hélios, Antiquité Merci pour votre écoute Un Jour dans l'Histoire, c'est également en direct tous les jours de la semaine de 13h15 à 14h30 sur www.rtbf.be/lapremiere Retrouvez tous les épisodes d'Un Jour dans l'Histoire sur notre plateforme Auvio.be :https://auvio.rtbf.be/emission/5936 Intéressés par l'histoire ? Vous pourriez également aimer nos autres podcasts : L'Histoire Continue: https://audmns.com/kSbpELwL'heure H : https://audmns.com/YagLLiKEt sa version à écouter en famille : La Mini Heure H https://audmns.com/YagLLiKAinsi que nos séries historiques :Chili, le Pays de mes Histoires : https://audmns.com/XHbnevhD-Day : https://audmns.com/JWRdPYIJoséphine Baker : https://audmns.com/wCfhoEwLa folle histoire de l'aviation : https://audmns.com/xAWjyWCLes Jeux Olympiques, l'étonnant miroir de notre Histoire : https://audmns.com/ZEIihzZMarguerite, la Voix d'une Résistante : https://audmns.com/zFDehnENapoléon, le crépuscule de l'Aigle : https://audmns.com/DcdnIUnUn Jour dans le Sport : https://audmns.com/xXlkHMHSous le sable des Pyramides : https://audmns.com/rXfVppvN'oubliez pas de vous y abonner pour ne rien manquer.Et si vous avez apprécié ce podcast, n'hésitez pas à nous donner des étoiles ou des commentaires, cela nous aide à le faire connaître plus largement. Hébergé par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

Galaxy Digital landed a 830 MW approval from ERCOT, and MrBeast gets a $200M investment from BitMine. Subscribe to the Blockspace newsletter! Welcome back to The Blockspace Podcast! Today, Colin and Charlie dig into Galaxy's 830 MW ERCOT approval for its Helios site, CleanSpark's latest land acquisition in Texas, BitGo's $1.96B IPO prospectus, Semler shareholders voting yes on the merger with Strive, and the first change to Bitcoin's BIP process in 9 years. Finally, for this week's (truly odd) cry corner: BitMine is investing $200M into YouTuber MrBeast (yes, really). Subscribe to the newsletter! https://newsletter.blockspacemedia.com Notes: * Galaxy Helios: 830MW approved * Clean Spark: 447 acres acquired * BitGo IPO: $1.96B valuation aim * BitMine: $200M to Beast Industries * Bitcoin Price: $97,000 recorded * Hash Price: Above $40/PH/Day Timestamps: 00:00 Start 02:17 Difficulty Report by Luxor 06:42 Galaxy 830 MW approval 10:30 CLSK land acquisition 15:37 BitGo IPO 19:00 ASST - SMLR deal approved 21:32 New BIP, who dis? 25:39 Cry corner: BMNR invests in MrBeast

On this episode Michelle chats about her 3 night stay at Universal's Helios Grand Hotel for the opening few days of Epic Universe in 2025. Join us in The Producers Club Follow us: LINKTREE     

Helios Herrera, se une a Yordi para compartir herramientas clave sobre productividad, éxito y cómo reprogramar nuestra mentalidad para alcanzar metas personales y profesionales.See omnystudio.com/listener for privacy information.

Aquí, cada episodio es una oportunidad para descubrir historias fascinantes y chismes emocionantes. Te traemos entrevistas exclusivas y compartimos anécdotas que seguro te harán sonreír. Además, ¡nos divertimos con juegos e interacción con los oyentes! Prepárate para disfrutar de una buena dosis de diversión y mantenerte al día con todo lo que está pasando en el mundo del entretenimiento.See omnystudio.com/listener for privacy information.

The International Association of Cryptologic Research held their regular election using secure voting software called Helios…and lost the keys to decrypt the results, leaving them with no choice but to throw out the vote and call a new election. Hilarity ensues. We welcome special guest Matt Bernhard who actually works on secure voting systems to explain which bits are homomorphically additive or not.Watch on YouTube: https://www.youtube.com/watch?v=euw_yqAQFI8Transcript: https://securitycryptographywhatever.com/2025/12/30/iacr-heliosLinks:- NYT: https://www.nytimes.com/2025/11/21/world/cryptography-group-lost-election-results.html- IACR Memo: https://www.iacr.org/news/item/27138- https://www.iacr.org/elections/- https://vote.heliosvoting.org/faq- https://github.com/Election-Tech-Initiative/electionguard- https://www.usenix.org/legacy/events/sec08/tech/full_papers/adida/adida.pdf- https://www.iacr.org/elections/eVoting/about-helios.html- https://www.iacr.org/elections/eVoting/- https://crypto.ethz.ch/publications/files/CrGeSc97b.pdf- https://electionguard.vote/- https://eprint.iacr.org/2025/1901- https://freeandfair.us/blog/open-free-election-technology/- https://www.starvoting.org/- https://mbernhard.com/"Security Cryptography Whatever" is hosted by Deirdre Connolly (@durumcrustulum), Thomas Ptacek (@tqbf), and David Adrian (@davidcadrian)

On today's FRIDAY FACEOFF episode, Toph and Vechs bring on JP Buckley, the VP of Sales & Business Development for Helios Hockey. Buckley joins us to talk about all of the awesome new features Helios will be rolling out in the new year. TEN MINUTES ON THE CLOCK STARTING NOW! We appreciate every listen, download, comment, rating, and share on your social sites! Follow us: IG: @HockeyThinkTank X (Twitter): @HockeyThinkTank TikTok: @HockeyThinkTank Facebook: TheHockeyThinkTank Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

We're checking into Universal Helios Grand Hotel to see if this Celestial Park stunner truly lives up to the hype. From gorgeous views and modern rooms to breezy pool vibes and a rooftop bar that practically begs you to stay all night, we're breaking down everything you need to know about Universal's newest Signature resort.But before we get too relaxed, we do the exact opposite of relaxing… and launch ourselves straight into the Upside Down for the Sandbox VR Stranger Things experience. If you've ever wondered what it feels like to be a freshly recruited Hawkins Lab test subject — complete with haptic vests, free-roam VR, and Vecna breathing down your digital neck — this one's for you. We'll walk you through the story, the scares, the teamwork chaos, the Demogorgon encounters, and of course… who on our team “carried the squad” (the after-action video never lies).From high-end luxury at Helios Grand to high-intensity thrills in Stranger Things VR, we're covering food, vibes, gameplay, pricing, and whether these two experiences are worth adding to your next Universal vacation.

In this bonus episode, we are sharing recordings from the Pursuit: The Founders' Guide to Happiness podcast launch event featuring a performance of Jeffrey Rosen's The Golden Mean: Songs for the Pursuit of Happiness and Twelve Titans: Songs of the Greek and Roman Gods and Goddesses in Philadelphia.   Jeffrey Rosen, author of The Pursuit of Happiness and host of the podcast, performs his original songs inspired by the book's exploration of the classical writers on virtue that shaped the founders.    This performance features Jeffrey Rosen and pianist Jennifer Blyth with arrangements by Greg Strohman.  Resources  Listen to Pursuit: The Founders' Guide to Happiness on ⁠⁠Apple Podcast⁠⁠ and ⁠⁠Spotify⁠⁠  Watch the full performance of the ⁠Pursuit of Happiness: Song Cycles⁠ by Jeffrey Rosen   Twelve Titans: Songs of the Greek and Roman Gods and Goddesses, music and lyrics by Jeffrey Rosen [PDF]  Jeffrey Rosen, ⁠The Pursuit of Happiness: How Classical Writers on Virtue Inspired the Lives of the Founders and Defined America⁠, (2024)   Jeffrey Rosen, ⁠The Pursuit of Liberty: How Hamilton vs. Jefferson Ignited the Lasting Battle Over Power in America⁠, (2025)   Timeline Twelve Titans: Songs of the Greek and Roman Gods and Goddesses [00:00] Episode Introduction  [01:14] Twelve Titans Introduction  [05:10] 1. Twelve Titans   [08:15] 2. Apollo, Helios, and Hyperion   [11:15] 3. Pythia   [14:49] 4. O Diana   [17:36] 5. Athena   [20:00] 6. Mighty Aphrodite   [22:42] 7. Mercury   [25:28] 8. The Three Fates   [28:25] 9. Apollo's Rising   [31:04] 10. Dame Fortune   [33:29] 11. Enthusiasmos   [36:16] 12. Divinity Is One  Stay Connected and Learn More Questions or comments about the show? Email us at ⁠⁠⁠⁠⁠programs@constitutioncenter.org⁠⁠⁠⁠⁠ Continue the conversation by following us on social media @ConstitutionCtr Explore the⁠⁠⁠⁠⁠America at 250 Civic Toolkit⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠Sign up⁠⁠⁠⁠⁠ to receive Constitution Weekly, our email roundup of constitutional news and debate Subscribe, rate, and review wherever you listen Join us for an upcoming ⁠⁠⁠⁠⁠live program⁠⁠⁠⁠⁠ or watch recordings on ⁠⁠⁠⁠⁠YouTube⁠⁠⁠⁠⁠ Support our important work ⁠⁠⁠⁠⁠⁠⁠Donate

SHOW SCHEDULE 10-17-25 CBS EYE ON THE WORLD WITH JOHN BATCHELOR THE SHOW BEGINS IN THE DOUBTS ABOUT COAL-FIRED ELECTRICITY FOR THE AI DATA CENTER BUILD OUT OF 26 GIGAWATTS BY 2035... 1912 COAL BREAKER BOYS FIRST HOUR 9-915 High-Tech Coal Mining and Its Role in the Future of AI Energy. Salena Zito discusses her visit to a high-tech coal mine 1,200 feet below Pennsylvania, highlighting modern, filtered, and pristine working conditions. The industry offers high-paying, generational jobs, even for those with advanced degrees. Coal, alongside natural gas and nuclear power, is vital for providing the reliable, strong base load energy required by new AI data centers and the defense industry. 915-930 High-Tech Coal Mining and Its Role in the Future of AI Energy. Salena Zito discusses her visit to a high-tech coal mine 1,200 feet below Pennsylvania, highlighting modern, filtered, and pristine working conditions. The industry offers high-paying, generational jobs, even for those with advanced degrees. Coal, alongside natural gas and nuclear power, is vital for providing the reliable, strong base load energy required by new AI data centers and the defense industry 930-945 Supreme Court Poised to Limit Racial Gerrymandering; War Powers Debate on Venezuela. Richard Epstein discusses how the Supreme Court appears ready to limit the use of race in drawing voting districts (racial gerrymandering), reflecting a shift towards colorblind jurisprudence. However, the Court is likely to avoid restricting political gerrymandering. Separately, Professor Epstein argued the president's use of "narcoterrorism" to justify military action in Venezuela is inappropriate, noting that the War Powers Act is often circumvented. 945-1000 Supreme Court Poised to Limit Racial Gerrymandering; War Powers Debate on Venezuela. Richard Epstein discusses how the Supreme Court appears ready to limit the use of race in drawing voting districts (racial gerrymandering), reflecting a shift towards colorblind jurisprudence. However, the Court is likely to avoid restricting political gerrymandering. Separately, Professor Epstein argued the president's use of "narcoterrorism" to justify military action in Venezuela is inappropriate, noting that the War Powers Act is often circumvented. SECOND HOUR 10-1015 LA/Portland Homeless Crisis and Wildfire Preparedness Debate. Jeff Bliss discusses how California hosts at least 50% of the nation's homeless, with numbers increasing, extending from downtown LA to Malibu. Homeless encampments pose a constant wildfire threat due to warming or arson fires. Developer Rick Caruso successfully protected his Palisades property by proactively investing in brush clearance, equipment, and private fire crews, offering a model for prevention. Portland also faces a severe homeless crisis and high office vacancy. 1015-1030 Saudi Nuclear Ambitions, US Defense Pact, and the SMR Investment Bubble. Henry Sokolski discusses how Saudi Arabia is negotiating a US defense pact while pursuing uranium enrichment capability for nuclear power. The US is reportedly urging South Korea to switch a planned Saudi reactor sale to an American Westinghouse model. Separately, the Small Modular Reactor (SMR) industry is seeing enormous private valuation with zero revenue, signaling a potential financial bubble. 1030-1045 SpaceX Launch Approval, Rocket Lab, and Global Space Industry Updates. Bob Zimmerman discusses how Space Force approved SpaceX's request to double launches to 100 per year and open a second launch site at Vandenberg, despite Coastal Commission opposition. Wall Street views Rocket Lab favorably due to many recent launch contracts, even though it's still developing the Neutron rocket and not yet profitable. Impulse Space shifted focus to a lunar cargo lander, using its Helios tug as a service module, seeking to meet NASA's need for efficient lunar cargo delivery. 1045-1100 SpaceX Launch Approval, Rocket Lab, and Global Space Industry Updates. Bob Zimmerman discusses how Space Force approved SpaceX's request to double launches to 100 per year and open a second launch site at Vandenberg, despite Coastal Commission opposition. Wall Street views Rocket Lab favorably due to many recent launch contracts, even though it's still developing the Neutron rocket and not yet profitable. Impulse Space shifted focus to a lunar cargo lander, using its Helios tug as a service module, seeking to meet NASA's need for efficient lunar cargo delivery.THIRD HOUR 1100-1115 Replaceable You: Skin Grafts, Bioprinting Organs, and the Science of Replacement Anatomy. Mary Roach discusses how third-degree burns destroy regenerative cells, causing severe disfigurement unless patched with allografts (temporary substitutes like cadaver or cod skin). Researchers are attempting to 3D print organs, currently in the "Wright Brothers stage," using specialized bio-ink and support gel. Xenotransplantation involves genetically editing pigs to grow human organs (chimerism) that the body would accept without rejection. 1115-1130 Replaceable You: Skin Grafts, Bioprinting Organs, and the Science of Replacement Anatomy. Mary Roach discusses how third-degree burns destroy regenerative cells, causing severe disfigurement unless patched with allografts (temporary substitutes like cadaver or cod skin). Researchers are attempting to 3D print organs, currently in the "Wright Brothers stage," using specialized bio-ink and support gel. Xenotransplantation involves genetically editing pigs to grow human organs (chimerism) that the body would accept without rejection. 1130-1145 Replaceable You: Skin Grafts, Bioprinting Organs, and the Science of Replacement Anatomy. Mary Roach discusses how third-degree burns destroy regenerative cells, causing severe disfigurement unless patched with allografts (temporary substitutes like cadaver or cod skin). Researchers are attempting to 3D print organs, currently in the "Wright Brothers stage," using specialized bio-ink and support gel. Xenotransplantation involves genetically editing pigs to grow human organs (chimerism) that the body would accept without rejection. 1145-1200 Replaceable You: Skin Grafts, Bioprinting Organs, and the Science of Replacement Anatomy. Mary Roach discusses how third-degree burns destroy regenerative cells, causing severe disfigurement unless patched with allografts (temporary substitutes like cadaver or cod skin). Researchers are attempting to 3D print organs, currently in the "Wright Brothers stage," using specialized bio-ink and support gel. Xenotransplantation involves genetically editing pigs to grow human organs (chimerism) that the body would accept without rejection. FOURTH HOUR 12-1215 Lancaster County Economy, Consumer Spending Rebound, and Data Center Expansion. Jim McTague discusses how local businesses in Lancaster County, like the Pancake House and Ephrata Precision Parts, show no recession weakness and report booming business. Consumer spending appears to be rebounding, with full shopping carts and aggressive buying observed at Costco and Walmart. Construction on data centers is underway in the county, contributing to economic expansion. Wall Street bubble talk is present, but markets are not yet characterized by widespread froth. 1215-1230 Italian Politics, Journalist Attack, and the History of St. Augustine in Pavia. Lorenzo Fiori discusses how Italian Prime Minister Giorgia Meloni was rudely defined as a "courtesan" by a prominent union leader following her diplomatic presence at the Gaza ceasefire signing. Journalist Ranucci, known for investigating politics and mafia-related business, survived a car bomb attack; he has been under guard since 2021. St. Augustine's remains are located in Pavia (south of Milan), moved there due to the LoMBARDY'S king's connection to Milan's Saint Ambrose. 1230-1245 Corporatism vs. Capitalism: Analyzing Rent-Seeking and Regulatory Capture. Julia Cartwright discusses how younger generations often confuse corporatism (entangled government and business) with true capitalism. Rent-seeking involves businesses investing in politics for favors, like healthcare industry lobbying for subsidies. Rent extraction is when politicians threaten costly action to force business compliance (e.g., CAFE standards or tariffs). Solutions include sunsetting subsidies and banning sole-source government procurement. 1245-100 AM Corporatism vs. Capitalism: Analyzing Rent-Seeking and Regulatory Capture. Julia Cartwright discusses how younger generations often confuse corporatism (entangled government and business) with true capitalism. Rent-seeking involves businesses investing in politics for favors, like healthcare industry lobbying for subsidies. Rent extraction is when politicians threaten costly action to force business compliance (e.g., CAFE standards or tariffs). Solutions include sunsetting subsidies and banning sole-source government procurement.

SpaceX Launch Approval, Rocket Lab, and Global Space Industry Updates. Bob Zimmerman discusses how Space Force approved SpaceX's request to double launches to 100 per year and open a second launch site at Vandenberg, despite Coastal Commission opposition. Wall Street views Rocket Lab favorably due to many recent launch contracts, even though it's still developing the Neutron rocket and not yet profitable. Impulse Space shifted focus to a lunar cargo lander, using its Helios tug as a service module, seeking to meet NASA's need for efficient lunar cargo delivery.

SpaceX Launch Approval, Rocket Lab, and Global Space Industry Updates. Bob Zimmerman discusses how Space Force approved SpaceX's request to double launches to 100 per year and open a second launch site at Vandenberg, despite Coastal Commission opposition. Wall Street views Rocket Lab favorably due to many recent launch contracts, even though it's still developing the Neutron rocket and not yet profitable. Impulse Space shifted focus to a lunar cargo lander, using its Helios tug as a service module, seeking to meet NASA's need for efficient lunar cargo delivery.

Narrator: Thomas Jones