Podcasts about Arm

The concept of Spotify trigger cities has been circulating for years, promising artists a magic formula for exponential growth. But where did this theory originate and does it hold any scientific merit? We delve into these questions, scrutinizing the theory's lack of a solid scientific foundation.   In this episode of Creative Juice, we discuss the Spotify Recommendation Engine and the scientifically bankrupt concept of Spotify trigger cities and why many artists have found themselves stuck in a vicious cycle of unfulfilled promises and stunted growth. Arm yourself with knowledge about how the Spotify algorithm actually works, not based on bad science, but based on what Spotify developers themselves say, and make informed decisions about your music marketing strategy!   If you're tired of chasing elusive growth strategies and ready to understand how Spotify truly works, this episode is a must-listen so that you can say goodbye to the misleading trigger cities theory, and hello to practical, effective growth strategies!   DISCOVER: Where The Theory Of Spotify Trigger Cities Originated And Why It Lacks A Scientific Basis What The Spotify Recommendation Engine Actually Is How The Trigger Cities Theory Has Negatively Impacted Artists And Bands For Years Why Growing An Audience Outside Of Your Native Country Is A Bad Starting Point The Data And Psychology Of Spotify Playlist Listeners   RESOURCES: Learn How To Grow On Spotify Inside IndiePRO Listen To IndieAward Winner,  Cryptic One! How the Spotify "Algorithm" ACTUALLY works Looking to expand your team or need marketing help? Apply to work with IndieX! Join Us In The Indepreneur Discord Server!

Dave and I give you a bicep workout to try. Let's have some fun with this. Give the workout a try this week and let us know how it goes. Plus Gear QA TIME STAMPS BELOW - Dave Crosland & Scott McNally

Check out SignalWire at: https://bit.ly/signalwirewan Make compliance easy with Kolide at: https://www.kolide.com/WAN Save time and automate your social media marketing! Check out Tailwind at https://lmg.gg/tailwind and get 50 free bonus Ghostwriter AI credits! Timestamps (Courtesy of NoKi1119) Note: Timing may be off due to sponsor change: 0:00 Chapters. 1:09 Intro. 1:33 Topic #1: CS:GO is no more, long lives CS 2. 2:48 History of CS, Source, Luke's experience. 9:36 Subtick, playing with Joe, volumetric smoke, recoil & shield. 16:00 Twitch & FP on CS recoil, Steam reviews, $40M in 40 minute. 22:06 Steam reviews, discussing CS 2 replacing CS:GO, a negative review. 32:50 BG3, Linus's BG3 review on Discord, BG3's tutorial, games reviews. 48:21 Yvonne's character choice, camera mod, game preference. 56:03 LTTStore's new desk pad. 57:06 Linus recalls a viewer's argument on using YT Superchats. 58:18 Creator's warehouse bread plushies ft. FP poll. 1:01:16 Merch Messages #1. 1:01:22 Would you wipe your controversies if you also wipe what you learnt from them?  1:03:44 Luke disagrees with FP Poll. 1:04:58 Any personal experience dealing with low temperature on tech? 1:07:23 New FP Poll for breads. 1:07:48 How many times has DLL said anything that caused chaos within LMG? 1:11:00 FP Poll result, bread is the meme. 1:12:09 Topic #2: Newegg's GPU trade in program. 1:12:34 Trade in prices, easy process & warranty. 1:20:49 Linus's price take, Luke on working with PayPal, LTT's AMD video, Linus on satire. 1:38:30 Sponsors. 1:42:13 Covering last WAN's supplement sponsorship. 1:45:30 Merch Messages #2. 1:45:36 How bad a monitor would you use for free before spending on one? 1:53:16 Has LTT ever used consultors or contractors? 2:00:56 How do you address technical debt in your projects? 2:06:00 Topic #3: Samsung's Neo G9 monitors cracking. 2:08:10 Luke on the low frequency of curved screens damage, Linus on per-region support. 2:12:08 Linus calls about if the Secret Shopper segment was shot, continues to leak. 2:22:16 Linus recalls Samsung's The Wall, purchases TCL's 115" MiniLED TV. 2:30:22 Linus's theory on why this is Chinese exclusive, LTT shot the Compensator. 2:35:30 Topic #4: Russian zero-day seller offers $20M to hack iOS & Android. 2:39:57 Topic #5: Reddit phases out gold & awards, now pays for karma. 2:42:08 Topic #6: Metaverse's 3D facial scan. 3:02:07 Topic #7: TheFloW teases a PS4/PS5 exploit. 3:03:39 Topic #8: Google will discontinue Podcast next year. 3:04:52 Topic #9: OpenAI's & Meta's new AI. 3:09:28 Topic #10: Getty's library generates images through an ethical database. 3:10:23 Topic #11: Google Search showcases ChatGPT-3's "eggs can be melted" response. 3:11:09 Topic #12: Military AI to sort U.S. intelligence. Cont. Topic #9: OpenAI's & Meta's new AI. 3:13:11 Meta's Ray-Band glasses article. 3:15:04 Luke shows Hotbunlover. 3:15:56 Merch Messages #3 ft. WAN Show After Dark. 3:16:58 How viable do you believe LTT's cleanest setup is? 3:19:48 Difficult challenge for tech that you've come to terms with? 3:20:41 Has Luke looked into aftermarket options for his car's infotainment system? 3:22:27 Has Linus's workload lowered after stepping down? ft. Tech shop sequel, Sea of Stars, cutscenes. 3:39:41 Did Yvonne's medical history  help her learn finance better? 3:40:16 Any noticeable LTTStore merch preference per region? 3:40:43 Do you see 12GB VRAM being enough for 2K Ultra settings in the future? 3:45:14 Is it true that Linus can leap over the chair from a standing position? 3:49:16 Arm wrestling on WAN Show? 3:50:18 Have you explored what it'd take to start an ISP? 3:50:52 What is Linus's favorite WAN Show snack? 3:51:22 Do you think you'll see AI reach full sentience in your lifetime? 3:52:32 Why does Luke stream his Starfield gameplay on Twitch and not on FP? 3:54:08 Outro.

In this enlightening episode, our host, Whitney Sewell, sits down with real estate savant and managing principal of ARM companies, Andy McQuade. With a quarter-century of industry experience under his belt, McQuade unveils his game-changing approach - The Total Cost of Ownership (TCO) Method.McQuade's expertise lies in empowering investors and operators to make informed property purchases that yield long-term benefits. This episode is a goldmine of insights as he delves into how the TCO method can lead to substantial savings by taking into account the comprehensive costs and benefits over time.For those navigating the multifamily real estate landscape, McQuade's insights are invaluable. Tune in to gain a fresh perspective and enhance your understanding of cost-effective property investment strategies.Don't miss the opportunity to connect with Andy McQuade, a mastermind in multifamily real estate, directly on LinkedIn. Engage with his wealth of knowledge and stay updated with his latest insights. Connect with Andy on LinkedInFor more in-depth resources and to learn more about his innovative TCO method, make sure to visit ARM Companies' official website. Discover how you can make smarter investment decisions today. Visit ARM Companies' WebsiteVISIT OUR WEBSITEhttps://lifebridgecapital.com/Here are ways you can work with us here at Life Bridge Capital:⚡️START INVESTING TODAY: If you think that real estate syndication may be right for you, contact us today to learn more about our current investment opportunities: https://lifebridgecapital.com/investwithlbc⚡️Watch on YouTube: https://www.youtube.com/@TheRealEstateSyndicationShow

Neste episódio, Américo Martins e Camila Olivo falam sobre o fim da autoproclamada República de Nagorno-Karabakh, cujo controle passa por gerações de guerras intermitentes e frágeis momentos de cessar-fogo entre Armênia e Azerbaijão.  O presidente Samvel Shahramanyan anunciou na quinta-feira (28) que o governo autônomo será dissolvido a partir de 2024, após o Azerbaijão lançar uma ofensiva bem-sucedida para retomar a região no Cáucaso. Para o geógrafo e professor de Geopolítica do Laboratório de Pesquisa em Relações Internacionais das Faculdades de Campinas (Facamp), James Onnig, o Azerbaijão venceu o conflito e agora vai iniciar um “processo de limpeza étnica” para acabar com a presença armênia na região. “Retomar Nagorno-Karabakh representa um papel simbólico do poderio do atual governo azerbaijano”, afirma o professor. Entre outros fatores, “aquela região pode ser utilizada para a passagem de gasodutos e oleodutos vindos do Mar Cáspio, que é um dos pontos mais importantes de exploração de hidrocarbonetos do planeta”, de acordo com James Onnig. Ouça também: Justiça de Nova York determina que o ex-presidente dos EUA, Donald Trump, cometeu fraude; o novo acordo contra a imigração nas fronteiras entre EUA e México; o ultimato do presidente do Paraguai, Santiago Peña, à União Europeia; e Rússia tenta voltar ao Conselho de Direitos Humanos da ONU.  Apresentação: Américo Martins e Camila OlivoProdução: Bruna SalesEdição: Raphael Henrique

European government bond prices dropped sharply as investors took fright at Italy's larger than expected budget deficit, optimism for the IPO market seems to be fading, and the FT's Colby Smith explains the economic impact of US student loan payments restarting. Mentioned in this podcast:European bond market hit by Italy's plans for higher borrowingRising headwinds threaten US economy's resilienceInstacart and Arm shares lose steam after IPO popsMillions of US borrowers brace for the return of student debt paymentsThe FT News Briefing is produced by Fiona Symon, Sonja Hutson, Kasia Broussalian and Marc Filippino. Additional help from Monique Mulima, Monica Lopez, Peter Barber, Michael Lello, David da Silva and Gavin Kallmann. Topher Forhecz is the FT's executive producer. The FT's global head of audio is Cheryl Brumley. The show's theme song is by Metaphor Music.Read a transcript of this episode on FT.com Hosted on Acast. See acast.com/privacy for more information.

Le forum de l'industrie de l'armement s'ouvre aujourd'hui a Kiev, en présence notamment du ministre français des Armées, Sébastien Lecornu. Il est venu avec une vingtaine d'entreprises spécialisées dans la production de blindés, d'artillerie, de drones... Envoyé spécial de RTL sur place, Morad Djabari a rencontré l'un de ces industriels français sur le point de s'installer en Ukraine.

Den Tower auf die Schulter, den viel zu großen und schweren Röhrenmonitor unter den Arm und ab dafür! Diesmal geht's bei uns um das Thema LAN-Partys. Ihr wisst schon: Stinkige Kellerräume, maximal ungesunde Ernährung und epische Schlachten über das Netzwerk. Viel Spaß mit unserem Ausflug in die Vergangenheit! ••• Diese Folge wird euch von unseren Freunden beim kicker präsentiert! Wer auf dem Laufenden bleiben will in Sachen eSport, checkt den eSport-Bereich auf kicker.de oder hört den kicker-eSport-News-Podcast "/gg", der zwei Mal im Monat erscheint und von Chris (Gürnth) und Nicole Lange vom kicker gehostet wird. ••• Timecodes: 00:00:00 Intro • 00:00:52 Vorgespräch • 00:42:48 Werbung: Disney+ (Simpsons Staffel 34) • 00:45:24 Vorgespräch • 01:23:06 Hauptthema: LAN-Partys • 02:06:17 Interview: Heiko Borchardt aka "Lazer" • 02:31:10 Hauptthema: LAN-Partys • 02:54:44 Interview: Nicole Lange (kicker) • 03:51:22 Hauptthema: LAN-Partys • 04:30:44 Tschüss!

About This EpisodeIn this episode, we delve into the bold founder's journey of Stephanie Sarka, the CEO and co-founder of 1 Atelier, a custom luxury brand dedicated to sustainability. Along the way, she shares her insights into the art of risk-taking and the importance of doing work that brings joy to you and to others. Having started in mergers and acquisitions, Stephanie quickly realized that she was more of a builder than a banker, and ultimately, went on to co-create the paid search model that has revolutionized the marketing and advertising industry and to found the custom luxury brand 1 Atelier. With her commitment to sustainability and the transformative power of technology, Stephanie has redefined what it means to be an innovative leader. About Stephanie SarkaStephanie Sarka is the Founder & CEO of 1 Atelier, the tech-enabled custom luxury brand which is disrupting the entire luxury experience and value chain. Graduating from Stanford, Stephanie started in M&A at Goldman Sachs. Realizing that she is a builder, not a banker, she spent a year running marketing for IFF in Paris before getting her MBA at HBS. She then worked at Coach for 7 years as Handbag Product Manager and GM of Mark Cross, the American luxury goods brand. Stephanie co-founded GoTo.com in 1998, where they invented the “Paid Search” business model. They took the company public in 1999 and grew it to ~$1 billion in revenue before selling it to Yahoo for $1.6 billion in 2003. This Fall, 1 Atelier is launching Farm to Arm, the first-ever luxury accessories offering that is carbon negative and biodegradable, as well as zero waste. Her mission is to heal the planet, one beautiful bag at a time. Additional ResourcesWebsite: https://1atelier.com/Check Out the New Collection Coming SoonInstagram: @1atelierluxuryLinkedIn: @StephanieSarka

Ano letivo arranca nas universidades angolanas, mas as aulas vão depender da boa-fé do Governo, avisa sindicato. Conflitos na região de Amhara podem gerar nova guerra na Etiópia, alertam especialistas. Mais de 50 mil pessoas já deixaram Nagorno-Karabakh para se refugiar na Arménia.

At one time—this was before the Robot Restriction Laws—they'd even allowed them to make their own decisions... Arm of the Law by Harry Harrison, that's next on The Lost Sci-Fi Podcast, with at least one lost vintage sci-fi short story in every episode. The Lost Sci-Fi Merchandise store is open for business. There are several designs and a multitude of t shirts, hoodies, sweatshirts, cups and pint size glasses so you can drink your favorite beverage while listening to the podcast. The link to our store is in the description and when you use the code in the description you get 15 percent off for a limited time. https://lostscifi.creator-spring.com  Use the coupon code EARLYBIRD and save 15% for a limited time. And in case you didn't hear the big announcement on our YouTube Live last week, there will be a new episode of The Lost Sci-Fi Podcast every day in October which starts Sunday.How could a robot—a machine, after all—be involved in something like law application and violence? Harry Harrison, tells what happens when a police robot hits an outpost on Mars. From the August 1958 issue of Fantastic Universe turn to page 132 for Arm of the Law by Harry Harrison... In two days on The Lost Sci-Fi Podcast, What happens when things go wrong at the Atomic Energy Commission? When meters stop working and there is no uranium? Is the enemy about to strike?The Pause by Isaac Asimov. That's in two days on The Lost Sci-Fi Podcast, with at least one lost vintage sci-fi short story in every episode.Support the show

Desde o fim da União Soviética, em 1991, Azerbaijão e Armênia disputam o controle de Nagorno-Karabakh — região internacionalmente reconhecida como território azeri, mas de população de maioria etnicamente armênia. Armênios que consideram a área como sua pátria ancestral. Em 1994, separatistas tomaram o poder, dando início a uma série de conflitos armados que se arrastam há mais de 30 anos. No capítulo mais recente, uma operação relâmpago das forças azerbaijanas retomou Nagorno-Karabakh, forçando o êxodo de mais de 50 mil armênios, quase metade da população local. À Armênia, o conflito não representa apenas uma disputa internacional, mas o resgate de uma memória traumática de seu povo, vítima do genocídio conduzido pelo império Turco-Otomano, no começo do século 20, responsável pela morte de cerca de 1,5 milhão de pessoas. O temor é de que uma nova limpeza étnica se avizinhe. Para entender a disputa em Nagorno-Karabakh e a tensão permanente na região do Cáucaso, Natuza Nery conversa com Filipe Figueiredo, graduado em história pela Universidade de São Paulo e autor do podcast Xadrez Verbal. Neste episódio: - Filipe, que esteve na Armênia em abril, relata como a ofensiva atual do Azerbaijão é vista pelos armênios como “uma retomada do genocídio de 1915, um trauma nacional coletivo”; - Ele conta que a operação das forças do Azerbaijão durou 24h, até que houvesse “uma intervenção diplomática, conduzida especialmente pelos Estados Unidos, que orientou a rendição das forças de autodefesa armênias na região”; - Filipe explica a principal reinvindicação dos armênios de Nagorno-Karabakh: eles “não tiveram direito à autodeterminação” no processo de elaboração das fronteiras após o fim da União Soviética, já que foram ignorados dois referendos em que a população local escolheu ser parte da Armênia; - O historiador também aponta o risco de que o conflito ganhe um novo capítulo, relacionado a Nakhchivan, enclave do Azerbaijão separado do resto do país pela Armênia, que liga a região a outras de influência turca.

durée : 00:03:31 - Le monde à 18h51 - par : Franck MATHEVON - Le Haut-Karabagh a annoncé sa dissolution au 1er janvier prochain. Les séparatistes arméniens renoncent au territoire après l'offensive de l'Azerbaïdjan. Plus de 70.000 Arméniens ont déjà fui la province. Et l'Azerbaïdjan a d'autres ambitions territoriales.

Last episode Paul and Ed talked about some IPOs that gave some indication that the public markets might be more open than we thought.  Current evidence (ARM stock chart and CART stock chat).Paul is wondering about recent Delta Air Lines changes and why more big companies don't become banks/credit card issuers.And, Ed has a poll up about whether Paul will actually buy a computer.We'd love it if you'd leave us a rating.  It takes less than a minute and really helps us out.  Just click here!If you've got a comment or question for the show, you can e-mail us at show@resultsjunkies.com.  You can find Paul and Ed  online @paulsingh and @pizzainmotion.

Ryan Dusick is an Associate Marriage & Family Therapist with an MA in Clinical Psychology and the founding drummer of the world's most popular band, Maroon 5. As a boy, he dreamt of pitching for the Dodgers and writing adventure novels. Arm injuries sidelined his burgeoning baseball career, just as rock music became his new passion and purpose. Founding the band Kara's Flowers in 1994 with fellow Brentwood High School students Jesse Carmichael, Mickey Madden, and Adam Levine, Ryan worked tirelessly through his college years at UCLA before the band changed its name to Maroon 5 and finally had its first hit record, Songs About Jane. Multiple hit songs, two Grammy Awards, and 20 million albums sold later, Ryan found himself suffering and without direction as his career as a performer came to an end, just as it was taking off. Struggling with physical and mental health challenges, Ryan finally overcame his struggles in 2016, when he began his journey of recovery, culminating in a new life path full of meaning, purpose, and fulfillment. Now working as a mental health professional at The Missing Peace Center for Anxiety in Agoura Hills, CA, Ryan is spreading the message that recovery is possible, and some astounding things can come with it.

durée : 00:14:52 - Journal de 8 h - Des représentants de l'Arménie et de l'Azerbaïdjan seront reçus ce mardi à Bruxelles par l'Union européenne, une semaine après la victoire éclair de Bakou dans le Haut-Karabakh et alors que 13 350 réfugiés de ce territoire sont déjà arrivés en Arménie.

Join host M.J. Kuhn as she delves into a mini-masterclass on Writing Mysteries with author Josiah Bancroft and (surprise!) our very own Adrian M. Gibson. During the episode, Josiah and Adrian investigate the clues of writing a mystery, including why we love a good mystery, the evolution of the genre, essentials like setting, atmosphere, hooks and capable protagonists, how to pace a mystery and dish out clues, cohesion and mysteries going off the rails, genre blending a mystery with SFF and more. NOTE: This is part two of a two-part chat with Josiah. Click ⁠here⁠ to check out part one. SUPPORT THE SHOW: - ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Patreon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ (for exclusive bonus episodes, author readings, book giveaways and more) - ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Merch shop⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ (for a selection of tees, tote bags, mugs, notebooks and more) - Subscribe to the ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠FanFiAddict YouTube channel⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, where this and every other episode of the show is available in full video - Rate and review SFF Addicts on your platform of choice, and share us with your friends EMAIL US WITH YOUR QUESTIONS & COMMENTS: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠sffaddictspod@gmail.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ABOUT OUR GUEST: Josiah Bancroft is the author of the new novel The Hexologists, as well as The Books of Babel series (Senlin Ascends, Arm of the Sphinx, The Hod King and The Fall of Babel). Find Josiah on ⁠Instagram⁠, ⁠Patreon⁠, ⁠⁠⁠Amazon⁠⁠⁠ and ⁠⁠⁠his personal website⁠⁠⁠.  ABOUT OUR HOSTS: Adrian M. Gibson is a podcaster, writer and illustrator, and is currently working on his debut novel. Find Adrian on ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ or ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠his personal website⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. M.J. Kuhn is the author of ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Among Thieves⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, her debut novel, and its sequel ⁠⁠⁠⁠⁠Thick as Thieves⁠⁠⁠⁠⁠⁠⁠⁠⁠. Find M.J. on ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TikTok⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ or ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠her personal website⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. FOLLOW SFF ADDICTS: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠FanFiAddict Book Blog⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ MUSIC: Intro: "⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Into The Grid⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠" by MellauSFX Outro: “⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Galactic Synthwave⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠” by Divion --- Send in a voice message: https://podcasters.spotify.com/pod/show/sff-addicts/message

O governo da Armênia informou nesta terça-feira (26) que cerca de 19 mil refugiados de Nagorno-Karabakh chegaram ao país depois que uma operação militar do Azerbaijão desmantelou forças separatistas da região. Os moradores do território, que fica dentro das fronteiras azeris mas é predominantemente habitado por armênios, temem uma limpeza étnica. O Durma com Essa conta o histórico do conflito e mostra a tensão entre o uso da força e da diplomacia entre os países envolvidos. O programa traz também Isabela Cruz comentando a corrida pela sucessão de Augusto Aras no comando da Procuradoria-Geral da República.Conheça nossos descontos de 60% para assinar o Nexo com o Google. É por tempo limitado!Assine o podcast: Spreaker | Apple Podcasts | Deezer | Google Podcasts | Spotify | Outros apps (RSS)Edição de áudio Pedro Pastoriz

durée : 00:14:52 - Journal de 8 h - Des représentants de l'Arménie et de l'Azerbaïdjan seront reçus ce mardi à Bruxelles par l'Union européenne, une semaine après la victoire éclair de Bakou dans le Haut-Karabakh et alors que 13 350 réfugiés de ce territoire sont déjà arrivés en Arménie.

Two miles of American front had gone dead. And on two lone infantrymen, lost in the menace of the fog-gas and the tanks, depended the outcome of the war of 1932, Tanks by Murray Leinster, that's next on The Lost Sci-Fi Podcast, with at least one lost vintage sci-fi short story in every episode. You asked for it and now it's here! The Lost Sci-Fi Merchandise store is open for business. There are several designs and a multitude of t shirts, hoodies, sweatshirts, cups and pint size glasses so you can drink your favorite beverage while listening to the podcast. The link to our store is in the description and when you use the code in the description you get 15 percent off for a limited time. https://lostscifi.creator-spring.com  Use the coupon code EARLYBIRD and save 15% for a limited time. And in case you didn't hear the big announcement on our YouTube Live last week, there will be a new episode of The Lost Sci-Fi Podcast every day in October which starts Sunday. This is the 3rd Murray Leinster story on the podcast. To say Leinster was prolific would be a vast understatement, having written more than 1,500 short stories and articles. Many of his short stories are longer than the short stories written by most vintage sci-fi authors. Let's go back in time almost 94 years ago to the January 1930 issue of Astounding Stories of Super­–Science. We'll find out story on page 100. Row after row of the monsters roared by, going greedily with hungry guns into battle. Tanks by Murray Leinster  In two days on The Lost Sci-Fi Podcast, At one time—this was before the Robot Restriction Laws—they'd even allowed them to make their own decisions... Arm of the Law by Harry Harrison. That's in two days on The Lost Sci-Fi Podcast, with at least one lost vintage sci-fi short story in every episode.Support the show

ARM Stock price has been extremely volatile ever since the company went public. ARM CPUs are mainly used in the mobile market, but thanks to AI, ML, and Cloud Computing, ARM stock might have other growth opportunities that can make it a reason to buy ARM Stock.A portion of this video is sponsored by The Motley Fool. Visit https://fool.com/jose to get access to my special offer. The Motley Fool Stock Advisor returns are 504% as of 9/8/2023 and measured against the S&P 500 returns of 130% as of 9/8/2023. Past performance is not an indicator of future results. All investing involves a risk of loss. Individual investment results may vary, not all Motley Fool Stock Advisor picks have performed as well. I have a position in $AMD $NVDASemiconductor Podcasthttps://www.fool.com/josenajarroDISCORD GROUP!! https://discord.gg/wbp2Z9STwitter: https://twitter.com/_JoseNajarroDISCLAIMER: I am not a financial advisor.  All content provided on this channel, and my other social media channels/videos/podcasts/posts, is for entertainment purposes only and reflects my personal opinions.  Please do your own research and talk with a financial advisor before making any investing decisions.

Arm und nicht mal sexy: Die Fed ist eigentlich pleite. Vor dem Hintergrund der in dieser Woche verkündeten Zinspause, nimmt sich Börsenreporterin Anne Schwedt die ganz eigene Bilanz der Federal Reserve vor. Wäre die Mutter aller Notenbanken ein Unternehmen, müsste sie Insolvenz anmelden. Die tiefroten Zahlen könnten schon sehr bald Folgen für den US-Haushalt haben und damit letztlich für Anleger. Danach ein Update vom IPO-Markt. Nach dem Corona-Koma geht es an der Wall Street inzwischen wieder Schlag auf Schlag mit neuen Börsengängen. Doch wie profitabel sind die wirklich für Anleger? Anschließend der Sprung nach Deutschland. Im Dax-Talk rückt Siemens Energy in den Mittelpunkt. Gegen den ohnehin schon gebeutelten Konzern werden offenbar gerade Sammelklagen vorbereitet. In der Community Corner wird die Frage beantwortet, wie an der Börse am besten vom Zinseszins profitiert werden kann. Dazu gibt's ein Rechenbeispiel mit Wow-Effekt. Und zu guter Letzt noch ein schneller Blick auf die wichtigsten Termine der neuen Handelswoche. Die komplette Ausgabe ist Teil der Pioneer-Membership. Wenn ihr noch nicht an Bord seid, könnt ihr unser gesamtes Portfolio zunächst testen, dazu gibt es ein spezielles Angebot, schaut einfach mal hier: https://www.thepioneer.de/willkommen

Intel held its annual Innovation event this week, and our friend Adam Patrick Murray from PC World was there. Now he's here to fill us in on all the details about the company's big shift to Meteor Lake and beyond, including the embrace of chiplet-style modular CPU design, their ever-shrinking process nodes, major changes to how the CPUs are named, their first "neural processing unit," how complicated it's getting to benchmark all this stuff, and more.Check out some of PCWorld's recent coverage of the topics from this ep:Meteor Lake Tech Tour Deep DiveHands-On With Core Ultra Laptops Running AI DemosIntel & The AI PC, NPU Performance, Developer Support & More | The Full Nerd Special EditionSupport the Pod! Contribute to the Tech Pod Patreon and get access to our booming Discord, your name in the credits, and other great benefits! You can support the show at: https://patreon.com/techpod

An episode in two parts. The first is an adventure story, the extraordinary march across Africa of a small detachment of French troops led by Major Jean-Baptiste Marchand. He occupied the abandoned Egyptian fort on the Nile at Fashoda. There he was met not by the planned supporting columns of Frenchmen, but by General Kitchener with a massively bigger force. In fact, the two men didn't fight, but met and were perfectly courteous with each other. It was up to the politicians in London and Paris to sort out the Fashoda incident. Given how precarious the French position was, inevitably it was resolved in favour of the intransigent British Prime Minister, who emerged with a British monopoly on access to the Nile in Sudan. Poor Marchand had to march away again having achieved very little, except to establish himself as a model for little boys to admire. The second part is about the other side of the coin of imperial Britain. That was the unbearable, crushing poverty in which a huge proportion of the population lived. Charles Booth, arguably the first Social scientist, established in his remarkable research that 30% of the population of London were living below the poverty line, and that line was a lot lower than it is today. Grandeur was the outward-looking face of Empire; behind the scenes, things were a lot uglier. Fashoda was just one critical incident for Britain in Africa. The next would be in South Africa. And the Empire would be looking for the men to fill the ranks of its army among just those poor, crushed by their misery and undermined by disease. Illustration: Jean-Baptiste Marchand on the cover of French magazine celebrating his march across Africa. © Paris - Musée de l'Armée, Dist. RMN - Grand Palais / Pascal Segrette 06-506187 / 2001.72.2 Music: Bach Partita #2c by J Bu licensed under an Attribution-NonCommercial-No Derivatives (aka Music Sharing) 3.0 International License.

Connaissez-vous notre site ? www.lenouvelespritpublic.fr Une émission de Philippe Meyer, enregistrée au studio l'Arrière-boutique le 22 septembre 2023. Avec cette semaine : Nicolas Baverez, essayiste et avocat. Jean-Louis Bourlanges, président de la Commission des Affaires étrangères de l'Assemblée nationale. Michel Eltchaninoff, rédacteur en chef du mensuel Philosophie Magazine. Lionel Zinsou, ancien Premier ministre du Bénin et président de la fondation Terra Nova. L'AGRESSION CONTRE LE HAUT-KARABAKH L'Azerbaïdjan a lancé le 19 septembre une opération militaire qualifiée par elle « d'antiterroriste » dans le Haut-Karabakh, territoire à majorité arménienne où la souveraineté de l'Azerbaïdjan est aujourd'hui reconnue et où les quelques 120.000 Arméniens qui y vivent jouissent d'une forme d'autonomie. Depuis la dislocation de l'Union soviétique, fin 1991, le Haut-Karabakh est un point de tension quasi constant Deux guerres meurtrières y ont déjà eu lieu, la première en 1988-1994 et la seconde en 2020, à l'issue de laquelle la Russie a déployé des forces chargées de garantir la libre circulation dans le corridor de Latchine, seul axe routier reliant le Haut-Karabakh à l'Arménie. Après une courte période d'accalmie, les tensions ont repris, Bakou menant une guerre d'usure à force de coupures de gaz, d'électricité, de tirs sur les paysans et de kidnappings. Fin 2022, les Azéris ont bloqué la circulation dans le corridor de Latchine. Ce blocus, renforcé en juillet, isole la population arménienne de l'enclave. Il a provoqué ces dernières semaines un début de famine. La Croix-Rouge n'est parvenue que le 18 septembre à faire passer une cargaison de vingt tonnes de farines et de produits médicaux. Les 2.000 soldats russes déployés dans l'enclave après le cessez-le-feu de 2020 et censés assurer la sécurité des Arméniens n'ont pas cherché à empêcher le blocus. Aucun pays ne reconnaît les autorités séparatistes arméniennes du Haut-Karabakh, pas même Erevan, qui les soutient. La première réaction publique du premier ministre arménien, Nikol Pachinian, a été d'écarter fermement l'option d'une intervention militaire de la République d'Arménie. Il a réaffirmé l'absence de soldats de son pays dans le Haut-Karabakh. Ces déclarations ont provoqué la colère de milliers d'Arméniens, qui sont venus manifester mardi devant le siège du gouvernement, à Erevan, pour affirmer leur solidarité avec les Arméniens du Haut-Karabakh et réclamer la démission de M. Pachinian. Mercredi, après 24 heures sous les frappes, les autorités arméniennes du Haut-Karabakh ont annoncé leur intention de déposer les armes, selon les conditions imposées par l'Azerbaïdjan pour toute négociation de cessez-le-feu. Le ministère azerbaïdjanais de la Défense a confirmé le désarmement des forces du Karabakh ainsi que l'ouverture de négociations en Azerbaïdjan. Les discussions porteront sur la réintégration de la région à population arménienne à l'Azerbaïdjan. L'opération militaire azerbaïdjanaise a fait au moins 200 morts et 400 blessés, d'après le dernier bilan des séparatistes arméniens, alors que 7.000 habitants auraient été évacués. *** LA FRANCE A-T-ELLE PERDU PIED EN AFRIQUE ? Les présidents de l'ex-pré-carré français en Afrique sont renversés les uns après les autres : le malien Ibrahim Boubacar Keita en août 2020, le guinéen Alpha Condé en septembre 2021, le burkinabé Roch Kaboré en janvier 2022, le nigérien Mohamed Bazoum au mois de juillet et fin août, le gabonais Ali Bongo. Dans la foulée de ces coups d'état, la France a dû évacuer ses militaires du Mali (août 2022), puis de Centrafrique (décembre 2022), du Burkina Faso (février 2023) et peut-être bientôt du Niger où elle déploie encore 1.500 militaires. Au Niger, le président français a choisi la fermeté : refus de reconnaître les autorités putschistes, exigence d'un retour au pouvoir du président Bazoum et rejet des injonctions de la junte, qui exige le départ de l'ambassadeur à Niamey et réclame le retrait des militaires français. Un mois après le coup d'État au Niger, la position de la France reste assez isolée. Joe Biden, qui veut sauver sa base militaire au Niger, ne voit pas d'inconvénients à dialoguer avec la junte. Les Allemands se désolidarisent de la position française au Niger, de même que les Italiens en Libye, tandis que les Espagnols reconnaissent le Sahara occidental pour se rapprocher du Maroc. Les pays d'Afrique de l'Ouest renâclent à intervenir militairement. La France est devenue indésirable dans ce qu'elle considérait jadis comme son « pré carré », décriée comme prédatrice économique par toute une génération et comme porteuse de valeurs honnies par des groupes islamistes orthodoxes et radicaux. Marquée du sceau colonial, la France vit d'autant plus mal son éviction de la région, qu'elle a le sentiment de s'être acquittée, à la demande des autorités locales, d'une tâche que les armées africaines ne parvenaient pas à remplir seules : la lutte antiterroriste contre le djihad. Le lent déclin de la présence française sur le continent se constate aussi sur le plan économique. La France n'est plus le premier fournisseur ni le premier investisseur du continent. Si, en valeur, les exportations françaises vers l'Afrique ont fortement augmenté, leur poids relatif a été toutefois divisé par deux, passant de 12 % de part de marché à 5 % entre 2000 et 2021. Pour Antoine Glaser, journaliste spécialiste de l'Afrique, et auteur de l'ouvrage « Le piège africain de Macron » « la France n'a pas vu l'Afrique se mondialiser, ni su solder sa présence post-coloniale, terreau du sentiment anti-français. Depuis la fin de l'opération Barkhane, le leadership français en Afrique est terminé. » Cependant, la ministre des Affaires étrangères, Catherine Colonna souligne que l'Afrique n'est pas que le Sahel. Elle assure que nos relations se développent avec des États dans lesquels nous étions moins présents, comme le Kenya, l'Afrique du Sud ou l'Éthiopie.Chaque semaine, Philippe Meyer anime une conversation d'analyse politique, argumentée et courtoise, sur des thèmes nationaux et internationaux liés à l'actualité. Pour en savoir plus : www.lenouvelespritpublic.fr

So now we're all standing largely naked before the coming onslaught of disinformation that is sure to come along with the 2023 and 2024 elections: the lies will be coming fast and furious. Are Trump's GOP opponents in an "Arm's race to out-extreme & out-cruel each other? Shutdown Watch! McCarthy hands the gavel to Gaetz as Jeffries tells the GOP, "We're not paying the ransom note" Holy Moly! Clarence Thomas secretly participated in Koch network donor events. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Carl Quintanilla, Jim Cramer and David Faber led off a busy program with markets after the worst day for the S&P 500 since March. Jim explained why he believes the markets are too negative and outlined the six reasons investors are selling stocks. The anchors also discussed what to make of the Apple iPhone 15 launch in stores worldwide. Also in focus: Deadline day for the UAW as it considers expanding its strikes against Detroit's "Big 3" automakers, Microsoft clears a key hurdle for its deal to acquire Activision, new stocks slump: Arm, Instacart and Klaviyo hovering around their respective IPO prices after strong opening day gains. Squawk on the Street Disclaimer

Cinquième et dernier épisode de notre série sur les conséquences du génocide des Arméniens de 1915. Il ne reste que quelques dizaines de milliers d'Arméniens aujourd'hui en Turquie. Ils ont survécu au gré du bon vouloir de lʹEtat et de ses options politiques. Histoire Vivante sʹintéresse aujourdʹhui à ceux qui sont restés sur les lieux du crime malgré la répression et lʹinjonction constante à lʹoubli. Avec Vicken Cheterian auteur Open Wounds, Hurst and Oxford University Press. Une série dʹAnaïs Kien Retrouvez toutes les séries dʹHistoire Vivante sur rts.ch/audio Histoire Vivante cʹest aussi tous les vendredis dans les pages de La Liberté et sur RTS 2, le dimanche soir.

Die Welt ist ungerecht, aber das muss sie nicht bleiben. Emissionshandel ist so ein Beispiel, da könnte man doch sehr leicht auch mal die Armen von profitieren lassen. Wie das gehen kann? Die WDR 2 Kabarettisten Jürgen Becker und Didi Jünemann mit einem Vorschlag. Von Jürgen Becker ;Didi Jünemann.

(0:00) Bestie intros! (3:05) GOP Primary update: polling, acceptable candidates, tentpole issues (11:56) All-In Summit 2023 recap (24:12) IPOs and M&A heat up: Arm, Instacart, and Klaviyo go public, Cisco acquires Splunk for $28B, but did the "great reopening" fall short? (42:34) Did the Fed break the VC model? How LPs will evaluate fund managers going forward (50:45) Breaking down Instacart and Klaviyo's businesses (1:01:12) Revaluing Airtable and the path forward for ZIRP-era unicorns (1:13:14) Fed pauses rate hikes, but says rates will stay higher for longer, plus: what breaks next in the economy? (1:32:51) Science Corner: new "inverse-vaccine" treatment is a potential game changer for autoimmune diseases Follow the besties: https://twitter.com/chamath https://linktr.ee/calacanis https://twitter.com/DavidSacks https://twitter.com/friedberg Follow the pod: https://twitter.com/theallinpod https://linktr.ee/allinpodcast Intro Music Credit: https://rb.gy/tppkzl https://twitter.com/yung_spielburg Intro Video Credit: https://twitter.com/TheZachEffect Referenced in the show: https://projects.fivethirtyeight.com/polls/president-primary-r/2024/new-hampshire https://youtu.be/yjj1QjZlQMM https://www.bloomberg.com/news/articles/2023-09-21/cisco-to-buy-splunk-for-157-a-share-in-28billion-deal https://twitter.com/pitdesi/status/1704874017357025499 https://www.google.com/finance/quote/ARM:NASDAQ?comparison=NASDAQ%3ACART%2CNYSE%3AKVYO&window=5D https://twitter.com/aswathdamodaran/status/1704246090198036914 https://cloudedjudgement.substack.com/p/clouded-judgement-81823-q2-earnings https://www.lendingtree.com/content/uploads/2023/08/ccs-chart-3-3.jpg https://fred.stlouisfed.org/series/MORTGAGE30US https://www.ey.com/en_gl/ipo/trends https://stockanalysis.com/ipos/statistics https://www.google.com/finance/quote/COIN:NASDAQ https://www.google.com/finance/quote/EXPE:NASDAQ https://www.axios.com/2023/09/19/instacarts-ipo-venture-capital https://www.sec.gov/Archives/edgar/data/1579091/000119312523221345/d55348ds1.htm https://influencermarketinghub.com/amazon-ad-revenue https://twitter.com/jasonlk/status/1704212644402540573 https://www.saastr.com/5-interesting-learnings-from-klaviyo-at-650000000-in-arr https://twitter.com/DavidSacks/status/1078755080478715904 https://i.insider.com/4dd4d1cf4bd7c8c90f000000 https://twitter.com/asanwal/status/1703492397739516068 https://www.cnbc.com/2023/09/20/fed-rate-decision-september-2023-.html https://tradingeconomics.com/commodity/crude-oil https://kalshi.com/markets/fed/fed-interest-rates#fed-23nov https://www.popularmechanics.com/cars/hybrid-electric/a42558850/tesla-price-cuts-worth-buying https://hellometer.io https://www.nature.com/articles/s41551-023-01086-2  

This week, we discuss why everyone is envious of Google's Internal Dev Tools, examine the state of Git, speculate about how 37 Signals plans to reinvent software licensing with ONCE, and share a few thoughts on the Salesforce CEO's recent comments about work from home. Watch the YouTube Live Recording of Episode (https://www.youtube.com/watch?v=AaX-PgF86bY) 433 (https://www.youtube.com/watch?v=AaX-PgF86bY) Runner-up Titles Lost in an acquisition hole. Headless Robot Dog. It's not better enough. GoogHub Why are you on the sad path Once version 2 is a paid upgrade You win interesting bingo Rundown The Full Circle on Developer Productivity with Steve Yegge (https://newsletter.pragmaticengineer.com/p/steve-yegge) Git is awful. GitHub isn't good enough. It's killing us! (Steve Yegge) (https://www.youtube.com/watch?v=EReooAZoMO0) Introducing ONCE (https://once.com/) Salesforce CEO takes a bold stand on remote work (https://www.thestreet.com/investing/salesforce-ceo-bold-stand-on-remote-work) Salesforce to Hire 3,300 People After Layoffs Earlier This Year (https://www.bloomberg.com/news/articles/2023-09-14/salesforce-to-hire-3-300-in-sales-engineering-data-after-earlier-job-cuts#xj4y7vzkg) Relevant to your Interests David Sacks has a new SaaS startup for other SaaS startups (https://www.axios.com/2023/09/06/david-sacks-has-a-new-saas-startup-for-other-saas-startups) Results of Major Technical Investigations for Storm-0558 Key Acquisition (https://msrc.microsoft.com/blog/2023/09/results-of-major-technical-investigations-for-storm-0558-key-acquisition/) Now it's PostgreSQL's turn to have a bogus CVE (https://opensourcewatch.beehiiv.com/p/now-postgresqls-turn-bogus-cve) HashiCorp Retools Licenses And Software To Grow Its Business - The Next Platform (https://www.nextplatform.com/2023/09/05/hashicorp-retools-licenses-and-software-to-grow-its-business/) Clouded Judgement 9.8.23 (https://cloudedjudgement.substack.com/p/clouded-judgement-9823?utm_source=post-email-title&publication_id=56878&post_id=136822157&isFreemail=true&r=2l9&utm_medium=email) Inside Hollywood's SBF Mad Scramble (https://theankler.com/p/inside-hollywoods-sbf-mad-scramble-c04?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axiosprorata&stream=top) Tubi The Free Streaming Service, Hits 74 Million Monthly Active Users & Almost 250 Free Live Channels As Cord Cutting Grows | Cord Cutters News (https://cordcuttersnews.com/tubi-the-free-streaming-service-hits-74-million-monthly-active-users-almost-250-free-live-channels-as-cord-cutting-grows/) IBM Software mandates return to office for those within 80km (https://www.theregister.com/2023/09/11/ibm_software_tells_workers_to/) Cloud is here to stay, but at what cost, ask customers (https://www.theregister.com/2023/09/11/cloud_costs_feature/) Disney and Charter reach deal to end cable blackout in time for 'Monday Night Football' (https://www.cnbc.com/2023/09/11/disney-charter-near-carriage-deal-that-would-end-cable-blackout-sources-say.html) Microsoft to kill off third-party printer drivers in Windows (https://www.theregister.com/2023/09/11/go_native_or_go_home/) Oracle revenue misses estimates as tough economy hurts cloud spending (https://www.reuters.com/technology/oracle-reports-quarterly-revenue-narrowly-below-estimates-2023-09-11/) No privacy in cars (https://foundation.mozilla.org/en/privacynotincluded/articles/its-official-cars-are-the-worst-product-category-we-have-ever-reviewed-for-privacy/) Former CEO of China's Alibaba quits cloud business in surprise move during its leadership reshuffle (https://abcnews.go.com/Business/wireStory/former-ceo-chinas-alibaba-quits-cloud-business-surprise-103078368) A Look Back at Q2 '23 Public Cloud Software Earnings (https://cloudedjudgement.substack.com/p/a-look-back-at-q2-23-public-cloud?utm_source=post-email-title&publication_id=56878&post_id=136950716&utm_campaign=email-post-title&isFreemail=true&r=2l9&utm_medium=email) 1 big thing: A long-term plan to secure open-source software (https://www.axios.com/newsletters/axios-codebook-8200e5c5-aed7-4f42-a40e-117a390b57e3.html?chunk=0&utm_term=emshare#story0) MGM takes systems offline after cyberattack (https://www.axios.com/newsletters/axios-codebook-8200e5c5-aed7-4f42-a40e-117a390b57e3.html?chunk=1&utm_term=emshare#story1) Disney-Charter deal represents new era for TV bundles (https://www.axios.com/newsletters/axios-media-trends-fe1295c8-9b83-4403-bae2-06de14fede11.html?chunk=2&utm_term=emshare#story2) Salesforce introduces Einstein Copilot Studio to help customers customize their AI | TechCrunch (https://techcrunch.com/2023/09/12/salesforce-introduces-einstein-copilot-studio-to-customers-customize-their-ai/) Arm prices IPO at $51 per share, valuing company at over $54 billion (https://www.cnbc.com/2023/09/13/arm-prices-ipo-at-51-per-share.html) Tim Gurner's spray about ‘arrogant' workers lays bare the economic sadism of our time (https://www.theguardian.com/commentisfree/2023/sep/14/tim-gurner-ceo-comments-more-unemployment-millionaire-property-developer-workers-neoliberals) Cisco discontinues Hyperflex hyperconverged infrastructure (https://www.theregister.com/2023/09/14/cisco_discontinues_hyperflex_hci/) CloudBees Announces New Cloud Native DevSecOps Platform (https://www.cloudbees.com/newsroom/cloudbees-announces-new-cloud-native-devsecops-platform) Jet: Prepare For Liftoff (https://www.jetporch.com/) Artifact's new Links feature makes it much more than a news app (https://www.theverge.com/2023/9/13/23871561/artifact-links-news-reading-app-tiktok) TriggerMesh, RIP (https://triggermesh-community.slack.com/archives/C02GHUAQDCH/p1695048539668859) Clorox says last month's cyberattack is still disrupting production (https://www.cnbc.com/2023/09/18/clorox-says-last-months-cyberattack-is-still-disrupting-production.html) Excel clone built for Uber China exposed Microsoft mistake (https://www.theregister.com/2023/09/19/matt_uber_china_excel_clone/) Seattle startup MotherDuck raises $52.5M at a $400M valuation to fuel DuckDB analytics platform (https://www.geekwire.com/2023/seattle-startup-motherduck-raises-52-5m-at-a-400m-valuation-to-fuel-duckdb-analytics-platform/) Google's Bard chatbot can now find answers in your Gmail, Docs, Drive (https://www.theverge.com/2023/9/19/23878999/google-bard-ai-chatbot-gmail-docs-drive-extensions) Elon Musk says X may go behind a paywall for everyone so he can 'combat vast armies of bots' (https://www.businessinsider.com/elon-musk-x-twitter-paywall-for-everyone-2023-9) Restricted Source Licensing Is Here (https://www.forrester.com/blogs/restricted-source-licensing-is-here/) OpenTofu (https://opentofu.org/) RoboFab is ready to build 10,000 humanoid robots per year | TechCrunch (https://techcrunch.com/2023/09/18/the-robots-are-coming/) Unified Acceleration Foundation Forms to Drive Open Accelerated Compute and Cross-Platform Performance (https://www.linuxfoundation.org/press/announcing-unified-acceleration-foundation-uxl) Google gets its way, bakes a user-tracking ad platform directly into Chrome (https://arstechnica.com/gadgets/2023/09/googles-widely-opposed-ad-platform-the-privacy-sandbox-launches-in-chrome/) What is a service mesh? Why do you need a service mesh? And which is the best service mesh? (https://newsletter.cote.io/p/what-is-a-service-mesh-why-do-you) Did I Make a Mistake Selling My Social-Media Darling to Yahoo? (https://nymag.com/intelligencer/2018/10/did-i-make-a-mistake-selling-del-icio-us-to-yahoo.html?utm_source=substack&utm_medium=email) A new way of thinking about open source sustainability (https://www.infoworld.com/article/3706508/a-new-way-of-thinking-about-open-source-sustainability.html) Elon Musk moving servers himself shows his 'maniacal sense of urgency' at X, formerly Twitter (https://www.cnbc.com/2023/09/11/elon-musk-moved-twitter-servers-himself-in-the-night-new-biography-details-his-maniacal-sense-of-urgency.html) Cable TV Is on Life Support, but a New Bundle Is Coming Alive (https://www.nytimes.com/2023/09/14/business/media/cable-tv-bundle-streaming.html) Nonsense McDonald's is getting rid of self-serve soda machines | CNN Business (https://www.cnn.com/2023/09/12/business/mcdonalds-self-serve-soda-machines/index.html) Delta SkyMiles changes: Delta overhauls how you earn Medallion status in biggest change yet (https://thepointsguy.com/news/delta-skymiles-changes/) Australian baby named Methamphetamine Rules (https://www.1news.co.nz/2023/09/20/australian-baby-named-methamphetamine-rules/) ‘Take the Money and Run' Artist Must Repay Danish Museum (https://www.nytimes.com/2023/09/19/arts/design/jens-haaning-take-the-money-and-run.html?smid=nytcore-ios-share&referringSource=articleShare) Listener Feedback Jan recommends this Rich Roll interview: Mindset SECRETS From The World's Best Ultrarunner: Courtney Dauwalter (https://www.youtube.com/watch?v=WOtSvYSnzNk) Conferences October 6, 2023, KCD Texas 2023 (https://community.cncf.io/events/details/cncf-kcd-texas-presents-kcd-texas-2023/), CFP Closes: August 30, 2023 November 6-9, 2023, KubeCon NA (https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/), SDT's a sponsor, Matt's there November 6-9, 2023 VMware Explore Barcelona (https://www.vmware.com/explore/eu.html), Coté's attending Jan 29, 2024 to Feb 1, 2024 That Conference Texas (https://that.us/events/tx/2024/schedule/) If you want your conference mentioned, let's talk media sponsorships. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us: Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk), Threads (https://www.threads.net/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: YouTube TV (https://tv.youtube.com/welcome/) and NFL Sunday Ticket (https://tv.youtube.com/learn/nflsundayticket/) An Endgame for YouTube TV, Big Disney Decisions (And Whether Bob Iger Should Make Them), The Era Beyond Peak TV (https://sharptech.fm/member/episode/an-endgame-for-you-tube-tv-big-disney-decisions-and-whether-bob-iger-should-make-them-the-era-beyond-peak-tv) Matt: Airline wifi chat with Support Coté: Do Interesting (https://thedobook.co/products/do-interesting-notice-collect-share) book by Russel Davis. Photo Credits Header (https://unsplash.com/photos/m-Yot4dUd6s) Artwork (https://unsplash.com/photos/I7iJOE4fsYo)

We are thrilled to announce the third session of our new Incubator Program. If you have a business idea that involves a web or mobile app, we encourage you to apply to our eight-week program. We'll help you validate your market opportunity, experiment with messaging and product ideas, and move forward with confidence toward an MVP. Learn more and apply at tbot.io/incubator. We look forward to seeing your application in our inbox! __ Co-host Will Larry interviews Stephen Hanson, the Director of Mobile Development at thoughtbot. The two explore the complexities of mobile app development, focusing on the advantages and disadvantages of React Native and Flutter. Stephen, who initially started as a full-stack web developer specializing in Enterprise Java, discusses React Native's cost-effectiveness and the convenience of having a unified codebase for iOS and Android platforms. However, he notes that Flutter might be a more suitable choice for high-performance needs. Both hosts emphasize the nuances of the mobile ecosystem, covering topics like in-app purchases, push notifications, and the strict guidelines set by app stores like Apple's. They agree that a comprehensive understanding of these aspects is crucial for an entire development team, including designers and project managers. Additionally, Stephen shares that the driving force behind his career is the opportunity to create apps that enhance people's lives. Stephen wraps up the discussion by detailing thoughtbot's goals of improving mobile development practices within the company and the broader developer community. __ React Native (https://reactnative.dev/) Flutter (https://flutter.dev/) Follow Stephen Hanson on LinkedIn (https://www.linkedin.com/in/hansonsteve/). Visit his website: shanson.co (https://shanson.co/). Follow thoughtbot on X (https://twitter.com/thoughtbot) or LinkedIn (https://www.linkedin.com/company/150727/). Become a Sponsor (https://thoughtbot.com/sponsorship) of Giant Robots! Transcript: WILL: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Will Larry. And with me today is Stephen Hanson, Director of Mobile Development here at thoughtbot. Stephen, thank you for joining me. STEPHEN: Hi, Will. Thanks for having me. I'm excited to be here. WILL: Yeah. I'm excited to talk about mobile development. But before we get started, tell us a little bit about who Stephen Hanson is: your personal life. STEPHEN: You know this because we often talk about our families when we get together. But I have two young kids, two and four years old. When you say personal life to anybody who has young kids, that's what we're talking about. [laughter] WILL: Yes. STEPHEN: So, they're keeping me busy but in the best way. WILL: Yeah, definitely. And I totally understand that. So, I know we talk about this often, but you like to woodwork. You like to work with your hands like most of us in tech. Like, we think so much with our head and mental that we try to find something to do physically, and yours is woodworking. Tell me a little bit about that. STEPHEN: Yeah. I think it's exactly what you said. I think working on a computer all day, you know, many years ago, I was like, what's something I can do with my hands, right? Something a little more physical. So yeah, fine woodworking has been a hobby of mine for quite a few years. And we were even chatting the other day about, you know, I'm trying to take time during the day to sneak out to the garage for 15 minutes, you know, during my lunch break or whatever to just get that mental reset and just work on something. WILL: Yeah. I know that you built your office that you work out of. I've been wanting to ask you, one, how did you do it? Two, how did you have the confidence to do it [laughter] to make sure that it was going to...how can I say this? I would be afraid that would it still be standing [laughter] after a little bit? [laughs] STEPHEN: Yeah, to be honest, that was definitely a fear. Yeah, I built my office in 2020, you know, COVID hit. All of a sudden, I was working fully remote. And we had another kid on the way. You know, we didn't have space in the house. So, I was like, what am I going to do? [laughs] I was already doing woodworking, but I didn't have any construction or carpentry experience. So, yeah, I definitely had the confidence issue. And I think, you know, I was just like, I don't know, let's just give it a try. [laughter] That's really all I can say. I didn't have the skills yet. But I watched a lot of YouTube and read a lot of [laughs] forums or, you know, just found info wherever I could, so...[laughs] WILL: Yep. And it's still standing today, correct? [laughs] STEPHEN: Correct. Yeah. [laughs] No, I'm just sitting in, like, a pile of rubble right now. [laughter] WILL: That's awesome, yeah. It's kind of like development sometimes for me. Like, you just got to take that leap sometimes, so... STEPHEN: You do, right? It's like, you know, fake it till you make it. [laughter] WILL: Yep. That's awesome. Awesome. Awesome. So, tell us a little bit about how did you get started in development in general? And then, how did you get started in React Native? STEPHEN: Yeah. So, I started out as a full-stack web developer. So, I didn't initially set out and say, "I'm going to build mobile apps," right? And I started out in 2011. I was working in Enterprise Java. I worked for American Airlines for a couple of years, and then I did enterprise consulting. I eventually made my way to, like, Rails and front-end development. And around 2016, 2017, I was freelancing. And eventually, clients started asking me to build mobile apps. [chuckles] WILL: [inaudible 04:16] STEPHEN: And I didn't know how to build mobile apps. So, I did what any web developer would do who doesn't build apps, and I used web technology. So, those first couple of apps that I built were hybrid apps. I used Ionic. And those are, you know, web apps that you package in a Native Wrapper. So, developing these apps, I literally developed them in a browser, right? And they're web apps. [laughs] And that was my first experience building apps. Even if they were web-based, I still had to work with the native app stores and learn, you know, app review guidelines and implement some native functionality, even though it was through, like, the Ionic wrappers. You know, people kind of trash on hybrid apps, and sometimes for good reason. But that wasn't a bad first experience for me or outcome, honestly. The clients were happy. They had apps in the app stores that were working for a pretty reasonable development cost. So yeah, that was my first experience in mobile. The end result isn't something I'd be necessarily proud of today. [laughs] WILL: I think that's all devs. [laughs] STEPHEN: Yeah, you know, [laughter] yeah, I -- WILL: Looking back at their work, yeah. [laughs] STEPHEN: I was talking about that. I could look back to something I built a month ago. [laughs] WILL: Yes. [laughter] STEPHEN: You don't have to go back far. [laughter] WILL: Yeah, so true [laughs]. You started working with the client when you were freelancing. So, how did you go from the hybrid web apps to actually saying, okay, I want to change, and I want to go all in on React Native? STEPHEN: React Native came out around that same time I was building those hybrid apps. So, the hybrid apps were 2016, 2017. React Native came out in 2015. So it was out, but it was still pretty new. And I was really interested in React Native right from the beginning, but I was also a little intimidated by it [chuckles]. So, when those first clients came to me for mobile apps, I didn't feel confident enough to say, "Yes, I can build you a React Native app." But a year or two later, I was working for another client on their Rails app. And I was building an API for their new React Native app. You know, I was really interested in React Native. So I said, "Hey, [chuckles] why don't I help out on the app side, too?" And they were like, "Sure, that sounds great." So that was kind of where I got my foot in the door with React Native. And then more opportunities like that just kept popping up over the next year. So, I got to work on a couple of other React Native apps. And like we talked about, I just started calling myself a React Native developer [laughs]. The rest is history. WILL: Yep. So true. We'll touch more on that later. But what would you say to a client who is trying to figure out if they should build native versus React Native? STEPHEN: There's a few things to consider when making that decision. But I think, usually, what I've seen is it comes down to budget and user experience. The bottom line is React Native is going to be a lot cheaper. You're basically building one app instead of two, right? Most of your code in a React Native app is going to be in JavaScript, and you can reuse all of that code across Android and iOS. If you're building a native app, you're just building two completely separate apps. So, it's just going to be cheaper to build that React Native app, and a lot of times, that's what it comes down to. For most companies, it can be really hard to justify that extra cost of building a completely native app for each platform. But then the question is when we talk about how can you justify the cost? Well, what would justify the cost, right? [laughs] I think probably the biggest trade-off when you build a React Native app versus a purely native app is there is a little bit of a performance penalty by building in React Native versus native. So, I think apps that will need to have a very flashy cutting-edge experience with lots of user-driven animation and effects, you know, when you get into that domain, I think that's where we see pure native starting to make more sense. But most apps and users would never feel that performance penalty of React Native. So, for most apps, that's not really something that enters into the equation. WILL: I want to dig into something you said. You were talking about if you do go native, you usually have to build an iOS and an Android separately. But with React Native, you could do it together. So, for someone who's maybe never done either one of them, can you kind of dig into, like, what does that look like? So, when you say I have to build an iOS and an Android portion versus I can do one codebase for React Native, can you walk us through kind of what that looks like, just a sample feature? STEPHEN: When I say React Native is a single codebase and, you know, native apps, you're building two apps, the way React Native works is you're basically building a React app. So, all of your business logic is going to be in React. And when your React code renders some UI, that gets translated into native UI. But your business logic is still going to be living in that JavaScript React app. So, one, when I say performance penalty, that's what I'm talking about is: there's a little bit of a performance penalty communicating back and forth between your JavaScript thread and the native system thread. But when we talk about one codebase versus two, that's what a React Native app looks like. You basically are working on a React app. It's one codebase with one set of business logic. And when you say, "Show a modal on the screen," that gets translated into a native Android modal or a native iOS modal, but in your code, you're just saying, "Show a modal." [laughs] So, you're just writing that one time. So yeah, a React Native project is just one codebase. Now, one thing that we haven't really touched on is in a React Native app, you do have the ability to drop down into native code. So, you have access to the native Android project and the native iOS project in your React Native app. So, you can write completely native code if you want to. But the appeal of React Native is you don't have to, you know, unless you get into one of those situations where you need to do something native that isn't supported out of the box with React Native or by an existing third-party library, or you want to have a very performant, very interactive part of your app. Maybe there's a reason you want to do that in native. You know, you do have that option in a React Native app of dropping down into that native code level. But to contrast that with a purely native project, you will have two completely separate codebases, one for Android and one for iOS. You'll have a development team for Android and a development team for iOS, you know, typically with different skill sets. The Android project will be Java, Kotlin. And your iOS project is swift. So, just in every sense, you really have two different projects when you're working on a purely native app. WILL: Okay, yeah, that makes sense. So like, for React Native, that show modal is just however many lines to show that one modal, and it does it for iOS and Android. But when you talk about native, you're saying that; however, iOS says to show that modal, you have to do it that way. But then Android, you also have to do it the Android way. And one developer, unless they know both of them, may not be able to handle both for those cases, correct? STEPHEN: Yeah, exactly. React Native abstracts away those underlying platforms. So, you really just need to know React Native for most cases. Though, there's definitely a benefit of knowing the underlying platforms. WILL: Definitely. Especially, like you touched on if you wanted to go into that native portion to add in a feature. You know, for example, I know we both worked on a project where we had a scanning app. And we had to tap into that native portion and React Native in order to get the scanning app to work, correct? STEPHEN: Yeah, that's right. We had to support some barcode scanning devices and hook into those barcode scanning frameworks that were proprietary [chuckles] to those devices. So yeah, we had to build native modules for Android and iOS to support those. WILL: Gotcha. Okay. I want to touch back on something you said earlier about the flashy experiences. You said sometimes you may not see it or whatever, but sometimes, if you want that flashy experience, it's better to go the native route. Can you explain that a little bit more? STEPHEN: So yeah, it's kind of what I was touching on a second ago. You know, in a React Native app, you have the JavaScript thread that is always running and coordinating UI changes with business logic. So, you've got your business logic in JavaScript. You've got the UI in native. And those need to be coordinated to interact. So, that's kind of where that performance penalty can happen. You know, again, most apps and users would never feel this penalty. I've never been, like, using my phone and been like, oh, this is a React Native app; I can feel it, you know. [laughs] It's not something that typically enters the picture for most apps that we work on. But there are certain types of apps that might be more important, you know, highly interactive games or things that just need to have that extra flashiness and interactive flashiness specifically, where it could make sense to build that natively. Another interesting thing in the React Native space is React Native recently re-architected their rendering engine to be written in C++ and be more efficient. So, this performance overhead might be a little bit less of a trade-off. They've re-architected the way that React Native JavaScript talks to the native layer, which might make this even less of an issue going forward. WILL: I looked it up for the podcast. But do you know some of the companies that we probably are familiar with, like they built apps on React Native? Can you name a couple? STEPHEN: Yeah, I was recently looking at this, too. And, you know, the big one is Facebook, right? Facebook built React Native. So, they're the sponsor of that project. So, Facebook and Facebook Messenger, I believe those apps are built with React Native. I don't know if the entire apps are or not [chuckles]. Do you know by chance? [laughs] WILL: React Native on their website says, "Hey, we're going to showcase these apps that they're built in React Native." So, I'm guessing a huge portion of it was built in React Native, so... STEPHEN: Yeah. That's a good point. Yeah, you're right. They're showcasing it there. So yeah, you know, other ones, you know, lots of brands, Shopify, looks like PlayStation. I'm looking at the list now on the React Native website: Pinterest, Flipkart, Discord, Walmart, Tesla, Coinbase, Mercari. Yeah, I mean, it's just a lot of big-name apps built in React Native, including quite a few that we've [laughs] that we've built. [laughter] MID-ROLL AD: Are you an entrepreneur or start-up founder looking to gain confidence in the way forward for your idea? At thoughtbot, we know you're tight on time and investment, which is why we've created targeted 1-hour remote workshops to help you develop a concrete plan for your product's next steps. Over four interactive sessions, we work with you on research, product design sprint, critical path, and presentation prep so that you and your team are better equipped with the skills and knowledge for success. Find out how we can help you move the needle at tbot.io/entrepreneurs. WILL: If I'm absolutely sold on getting that flashy experience, is native the only route to go? STEPHEN: I think until pretty recently, that would have been your option [laughs]. But Flutter has been picking up a little bit of momentum. So, Flutter is developed by Google. And it's kind of a challenger in that React Native space. It kind of has the same write once, run anywhere, you know, philosophy as React Native. You have one codebase. But they tout kind of being a more performant option than React Native. So, it compiles down to native ARM or Intel code, which can give better performance without, you know, not needing that JavaScript bridge kind of handling that communication between the UI and the business logic. WILL: So, when would you use Flutter versus React Native? STEPHEN: I kind of keep going back to, like, you know, we talk about the performance overhead of a React Native app. I don't think that's even on the map for the vast majority of apps. Like, this isn't a performance penalty that you can typically feel. So, looking at Flutter versus React Native, React Native has several advantages. I think the biggest one is it's React. So, every team has React developers already on the team, pretty much nowadays. So, you know, if you've got an organization that says, "Oh, we need to build a mobile app," they probably already have a team of React developers somewhere working on their web app [laughs]. So, there's a big benefit of kind of centralizing their team around that technology. You know, you can have a little bit of cross-pollination between web and mobile, which can be really nice. I think, similarly, it's a lot easier to find and hire React or React Native developers right now than it is to find and hire Flutter developers. So, Flutter is written in Dart, and it has its own front-end framework. So, this isn't necessarily a technology that you're going to have on your existing team. Like, I've never worked with Dart, personally. It's not nearly as common as React developers. You know, that, to me, is going to be a big downside. You know, the talent pool is a lot smaller for Flutter/Dart developers. Also, the ecosystem with Flutter being newer, it's not as established. It doesn't have as large of an ecosystem as React Native. So, for those reasons, I think React Native is still, at least for us, like, it's usually where we would steer a client over Flutter, unless they're in that category of, like, they're really going for something, you know, groundbreaking. And, you know, the choice is either, you know, they've ruled out React Native. They need to get that native performance, and maybe they could achieve that with Flutter, and maybe Flutter would be a good option then. WILL: Okay. You mentioned that—and I agree with you—like, you probably have some React devs on your team somewhere. Most companies does. So, say if I am bought in, I'm going all in on React Native, and I have React web developers on my team. Is that an easy transition for those developers, or what does that transition look like? STEPHEN: Yeah, this is something...I think you and I have talked about this a lot because we both transitioned from React Web to React Native. And, you know, it wasn't all that easy, right? [laughs] WILL: No, it was not [laughter] at all. [laughter] STEPHEN: So yeah, you know, it is a fallacy to say, "Hey, we've got a React team, you know, let's just start tomorrow on building an app, and it'll be smooth sailing. And, you know, no one needs to learn anything, and we'll be good to go," right? [laughs] So, you know, what I always say is a React web developer can successfully work on a React Native app. But I don't think they have the skills yet to lead that initiative because there's just so much to the mobile ecosystem that needs to be learned. And really, you know, my first couple of React Native apps, I wasn't the lead developer. There was somebody on those projects who really knew that space better than I did. And that was really helpful for me to have. How about you? What about your first, like, React Native project? What did that look like? WILL: It was at another company, and the exact words paraphrasing was, "You know React, so you can easily work on React Native." And so, I got on the project. And I really struggled, to be honest with you, because there's a lot of things that I didn't know: in-app purchases, push notifications, how to deal with Apple store, Android store, deploying to those stores. Like all of those things, navigation is totally different than React navigations and routes. It was a lot. It was a lot more than they led on to what it was. Eventually, I caught on. It took me a while. I needed to work with some more senior React Native developers, and I was able to really pick it up. But yeah, it was tough. I'll be honest: I struggled for a while because I went in feeling like I should have known all those things because that's the way it was conveyed to me. Now that I look back on it I was like, there's no way I could have known those things. It's just a different language. So, I had to get in there and learn it. And I even...I'm trying to think I've learned a couple of new languages. But it's almost like learning a new language just with, you know, the, like I mentioned, the in-app purchases, push notifications. It's just totally different. STEPHEN: Yeah, that's been my experience also. I think the challenges weren't, like, coding [laughs] because, you know, building a React Native app is coding in React. The challenges that I faced were, like you said, it's just the mobile ecosystem and learning all the intricacies, the functionality that users have come to expect in mobile apps, you know, like password manager, integration, and background execution modes, and deep linking strategies, all that kind of stuff. You know, if you don't know what questions to ask or what features to be thinking of, it's just really hard. And [laughs] I think it's more than just the developer needing to know that too. I think anytime it comes, you know, down to building an app, the whole team needs to have that mobile background. It's just a completely different platform than building for the web, right? So like, product owners, project managers, designers, developers all need that context so we can be prioritizing the right features and building a UI that matches the patterns that people have come to expect in a mobile app. And then, of course, developing those apps using the, you know, the proper native modules. WILL: Yeah, definitely. And I [chuckles]...you mentioned that it's mostly on, like, the mobile side. I don't know the best way to say that. But, like, I can tell you, when I first got onto the React Native project, there were numerous features that I could implement, and to a certain point to where I had to go that mobile. So, like, I was like, oh yeah, I can learn these new components that's in React Native. Okay, I got it to work. It's finished. You know, my PM would be like, "Well, it's not completely finished because you have to deploy it." And I was like, oh, I have no idea what I'm doing now. Like, I just know [laughs]...I know up to this point. STEPHEN: [laughs] WILL: But anything over that, I'm like, yeah, I have no idea. STEPHEN: Especially with consulting, right? With consulting, you need even more expertise, right? The clients are counting on you to build their app. And that's where, you know, having that deep, deep familiarity where you can say to a client, "This is how we're going to do the deployment process, you know, and I need, you know, X, Y, and Z to help set it up. And here are the deliverables, and here's when we'll have it," that kind of thing. Like, it really takes it up a whole nother notch what you need to know. WILL: Definitely, yeah. Because I think compared to mobile, I feel like web development can almost be like the Wild Wild West. And what I mean by that is, like, there's no rules for you to push out a website in web. Like, you know, you build it. You push it out. It can be out there, you know. Whoever is hosting it, unless you go against their rules, maybe, but their rules are very relaxed and stuff like that. Mobile, there's a totally different set of rules. Because, like, I was laughing not too long ago. There was rumors that Elon Musk was going to remove the blocking feature on Twitter [chuckles]. And it was funny because all the mobile devs they came out. And if you're a mobile dev, you know this. Apple is very strict. STEPHEN: [laughs] WILL: If this is a social media app that you're building, you have to have that blocking feature, which I agree it needs to be there. But it's funny, like, all the mobile devs was like, yeah, that's not going to work. Good luck [chuckles]. Good luck being an app again. STEPHEN: Yeah, [laughs] good luck. WILL: Like, they're going to kick it off. And yeah, they're very big on kicking it off if it doesn't follow those rules and things like that. So yeah, for React Native, you have to learn those rules, or, like I said, they won't approve it. They won't push it out to their store. STEPHEN: Yep, exactly. Yeah. I feel like the new one at every client project; I have to say, "We have to offer a way to delete your account in the app," because [laughs] that's a new one that launched last year, and I think has just started being enforced more recently. Like, all those little gotcha rules, you know, like, if you don't know about that, then you're going to go to submit your app to the stores, and you're going to get rejected every single time. [laughs]. WILL: And they're not shy about rejecting you [laughs]. STEPHEN: Yeah. But I would say, like, a lot of the rules, I'm like, yes, this is amazing that we have these rules, you know. It does help keep the community safer like things like blocking. But then there's the other rules of, like, Apple's like, hey, you've got to use our payment system and pay us 30% of every sale. WILL: Yes [laughs]. STEPHEN: I was, like, you know, there's some evil stuff happening there, too. WILL: I totally agree. And we ran into that issue. We had an app that used Stripe. And we actually had to remove it in order to use in-app purchases because...I forgot the rules around it, but it was essentially for digital content. I think it's what it was. And so, we had to use Apple's in-app purchases. So yeah, I totally agree with you on that. STEPHEN: Yeah. I feel like I've been a part of so many apps where we're, like, reading those rules. And we're like, okay, you know, it's like, we're watching a live stream of birds. WILL: [laughs] STEPHEN: You know, like, the birds aren't digital [laughter], you know. It's like, [laughs] where does this fall in the rule? [laughs] WILL: Yes [laughs]. I've done that, too [laughter]. Yep. It's almost like, you know, I feel like lawyers, okay, like, is this what this rule is, or the law what is written, or does this fall underneath that? So yeah, totally, totally agree. STEPHEN: Yep [laughs]. WILL: So, you've been here a couple of years at thoughtbot. What has been your experience building React Natives here for clients at thoughtbot? STEPHEN: Yeah, yeah. I've been at thoughtbot for about five years now. And I have been building React Native apps that whole time. And, I mean, I started at thoughtbot a little more in the full-stack space, web development, and have transitioned to where I'm mostly only building React Native mobile apps now. It's been a great experience. I think that React Native is really a sweet spot of; we're able to build these apps really efficiently and much less expensively than when we're doing pure native. And the end product is a really good app. So, it's been a great experience, you know, React Native is really...it has a really nice development experience. You know, it's the JavaScript React ecosystem. And we use TypeScript, and we have a really good developer experience with it. And then we're building apps that clients are really happy with and with a good budget. So, I think it's kind of that, you know, like, win-win-win kind of scenario where everybody is happy. And yeah, I don't see it going anywhere. And I think we're going to be building React Native apps for quite a while to come. WILL: Yeah, I totally agree with that. Where do you see React Native and mobile dev going here at thoughtbot in the next six months or even the next year? What are your goals for the mobile team? STEPHEN: We've got a couple of goals. One of them is around kind of what we've talked about with the mobile space in general. This isn't really specific to React Native, but it can be. But, consulting in the mobile space is challenging because there's a lot of mobile-specific domain knowledge that a team really needs to have. So, that's something that we've started looking into is, like, how do we build up our resources internally and then, hopefully, externally as well to help guide us on our projects and ensure that we have, like, you know, we are developing apps consistently and efficiently every time? So, that's something we're looking into is, like resources to help our teams—not just developers, but project managers, designers, and developers—help us navigate the mobile space. Okay, you're going to do push notifications. Here's the library we use. Here's things to think about, and interactions to think about, and iOS-specific functionality that we could support, and Android-specific functionality that we can support. You know, you're going to do deep linking; do you want to use universal links, or do you want to use a different strategy, a scheme-based link? So, basically, building up that set of resources so that our teams are all able to consult and build efficiently and consistently across the board. So, that's kind of goal number one. And then, goal number two is to kind of bring some of that out into the community a little bit more. So, thoughtbot is very well known in the Rails space for all of the open-source content we've put out and blog posts, and courses, and books. I mean, there's just so much on the Rails side that thoughtbot has done. And we're just a little bit less mature on the React Native side in terms of what we've put out there. So, that's kind of the second goal is giving back, helping others kind of do that same thing. I feel like we have developed our practices internally, and we're building some great apps. And it's kind of time to contribute back a little bit more. WILL: Awesome. I'm looking forward to reaching those goals. If you can go back and give yourself advice, what would you tell yourself? STEPHEN: I would maybe say, read the documentation [laughs]. I don't know when I got into mobile; I think I just jumped in. And, you know, we've talked about some of the mobile-specific domain, and not knowing what you don't know, and app review guidelines. I feel like early on, I just responded to challenges as they came up, as opposed to just digging into, you know, Apple's documentation and Android's documentation and just really understanding the underlying operating systems in stores. That's probably a piece of advice. If I could go back, I would just start at the documentation, you know, go to developer.apple.com and read about all of the underlying APIs of StoreKit and, you know, associated domains and all of these sorts of things. Just learn 'em, and then you know 'em. [laughs]. So, maybe that could have saved me some heartache if I just was a little more intentional about, okay, I'm getting into app development. I'm going to set aside some time and just really learn this stuff, as opposed to kind of where I had one foot in the door, one foot out of the door for a while. And I think that kept me from just sitting down and really going deep. WILL: That's really good advice. Just read the documentation. And that's not just Apple. STEPHEN: [laughs] WILL: That's a lot of departments, sections of my life. So, yes, I like that. [laughter] STEPHEN: I actually...that's something I did early in my career. So, I started as an Enterprise Java developer in 2011, and I was using the Spring framework. I downloaded the entire PDF. It was, like, 250 pages, the documentation [laughs]. And I remember just being on, like, airplane flights, and I just read the documentation, just cover to cover. That served me so well. I was, like, the expert, you know [laughs]. I don't always do it, but when I do, I'm like, oh yeah, why didn't I do that sooner? [laughs] WILL: Yeah, totally agree. I like that. What is the wind in your sails? What motivates Stephen? STEPHEN: Like, I think what attracted me to software development is just being able to build stuff, you know, probably the same thing that attracted me to woodworking. So, I think what motivates me is that prospect of, hey, I'm building an app that people are going to use, and it's going to make their life better. So, that's really what gets me up and gets me motivated. It's less so the actual coding, to be honest. It's really the prospect of, like, hey, I'm building something. WILL: Awesome. Yeah. Is there anything that you would like to promote? STEPHEN: If you're interested in building a mobile app, come talk to us. We'd love to build your mobile app. Go to thoughtbot.com/hire-us; I believe hire-us. We would love to talk to you about your mobile project. So, don't hesitate to reach out. We'd love to hear about what you're interested in building. WILL: Awesome. Well, Stephen, it was great to chat with you. It's always great to chat with you about mobile development and just personal life things. So, I really appreciate you being on the podcast today. STEPHEN: Thanks for having me, Will. It was a lot of fun. Always good talking with you. WILL: You can subscribe to the show and find notes along with a complete transcript for this episode at giantrobots.fm. If you have any questions or comments, email us at hosts@giantrobots.fm. You can find me on Twitter @will23larry. ANNOUNCER: This podcast is brought to you by thoughtbot, your expert strategy, design, development, and product management partner. We bring digital products from idea to success and teach you how because we care. Learn more at thoughtbot.com. Special Guest: Stephen Hanson.

Steve Tuck, Co-Founder & CEO of Oxide Computer Company, joins Corey on Screaming in the Cloud to discuss his work to make modern computers cloud-friendly. Steve describes what it was like going through early investment rounds, and the difficult but important decision he and his co-founder made to build their own switch. Corey and Steve discuss the demand for on-prem computers that are built for cloud capability, and Steve reveals how Oxide approaches their product builds to ensure the masses can adopt their technology wherever they are. About SteveSteve is the Co-founder & CEO of Oxide Computer Company.  He previously was President & COO of Joyent, a cloud computing company acquired by Samsung.  Before that, he spent 10 years at Dell in a number of different roles. Links Referenced: Oxide Computer Company: https://oxide.computer/ On The Metal Podcast: https://oxide.computer/podcasts/on-the-metal TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is brought to us in part by our friends at RedHat. As your organization grows, so does the complexity of your IT resources. You need a flexible solution that lets you deploy, manage, and scale workloads throughout your entire ecosystem. The Red Hat Ansible Automation Platform simplifies the management of applications and services across your hybrid infrastructure with one platform. Look for it on the AWS Marketplace.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. You know, I often say it—but not usually on the show—that Screaming in the Cloud is a podcast about the business of cloud, which is intentionally overbroad so that I can talk about basically whatever the hell I want to with whoever the hell I'd like. Today's guest is, in some ways of thinking, about as far in the opposite direction from Cloud as it's possible to go and still be involved in the digital world. Steve Tuck is the CEO at Oxide Computer Company. You know, computers, the things we all pretend aren't underpinning those clouds out there that we all use and pay by the hour, gigabyte, second-month-pound or whatever it works out to. Steve, thank you for agreeing to come back on the show after a couple years, and once again suffer my slings and arrows.Steve: Much appreciated. Great to be here. It has been a while. I was looking back, I think three years. This was like, pre-pandemic, pre-interest rates, pre… Twitter going totally sideways.Corey: And I have to ask to start with that, it feels, on some level, like toward the start of the pandemic, when everything was flying high and we'd had low interest rates for a decade, that there was a lot of… well, lunacy lurking around in the industry, my own business saw it, too. It turns out that not giving a shit about the AWS bill is in fact a zero interest rate phenomenon. And with all that money or concentrated capital sloshing around, people decided to do ridiculous things with it. I would have thought, on some level, that, “We're going to start a computer company in the Bay Area making computers,” would have been one of those, but given that we are a year into the correction, and things seem to be heading up into the right for you folks, that take was wrong. How'd I get it wrong?Steve: Well, I mean, first of all, you got part of it right, which is there were just a litany of ridiculous companies and projects and money being thrown in all directions at that time.Corey: An NFT of a computer. We're going to have one of those. That's what you're selling, right? Then you had to actually hard pivot to making the real thing.Steve: That's it. So, we might as well cut right to it, you know. This is—we went through the crypto phase. But you know, our—when we started the company, it was yes, a computer company. It's on the tin. It's definitely kind of the foundation of what we're building. But you know, we think about what a modern computer looks like through the lens of cloud.I was at a cloud computing company for ten years prior to us founding Oxide, so was Bryan Cantrill, CTO, co-founder. And, you know, we are huge, huge fans of cloud computing, which was an interesting kind of dichotomy. Instead of conversations when we were raising for Oxide—because of course, Sand Hill is terrified of hardware. And when we think about what modern computers need to look like, they need to be in support of the characteristics of cloud, and cloud computing being not that you're renting someone else's computers, but that you have fully programmable infrastructure that allows you to slice and dice, you know, compute and storage and networking however software needs. And so, what we set out to go build was a way for the companies that are running on-premises infrastructure—which, by the way, is almost everyone and will continue to be so for a very long time—access to the benefits of cloud computing. And to do that, you need to build a different kind of computing infrastructure and architecture, and you need to plumb the whole thing with software.Corey: There are a number of different ways to view cloud computing. And I think that a lot of the, shall we say, incumbent vendors over in the computer manufacturing world tend to sound kind of like dinosaurs, on some level, where they're always talking in terms of, you're a giant company and you already have a whole bunch of data centers out there. But one of the magical pieces of cloud is you can have a ridiculous idea at nine o'clock tonight and by morning, you'll have a prototype, if you're of that bent. And if it turns out it doesn't work, you're out, you know, 27 cents. And if it does work, you can keep going and not have to stop and rebuild on something enterprise-grade.So, for the small-scale stuff and rapid iteration, cloud providers are terrific. Conversely, when you wind up in the giant fleets of millions of computers, in some cases, there begin to be economic factors that weigh in, and for some on workloads—yes, I know it's true—going to a data center is the economical choice. But my question is, is starting a new company in the direction of building these things, is it purely about economics or is there a capability story tied in there somewhere, too?Steve: Yeah, it's actually economics ends up being a distant third, fourth, in the list of needs and priorities from the companies that we're working with. When we talk about—and just to be clear we're—our demographic, that kind of the part of the market that we are focused on are large enterprises, like, folks that are spending, you know, half a billion, billion dollars a year in IT infrastructure, they, over the last five years, have moved a lot of the use cases that are great for public cloud out to the public cloud, and who still have this very, very large need, be it for latency reasons or cost reasons, security reasons, regulatory reasons, where they need on-premises infrastructure in their own data centers and colo facilities, et cetera. And it is for those workloads in that part of their infrastructure that they are forced to live with enterprise technologies that are 10, 20, 30 years old, you know, that haven't evolved much since I left Dell in 2009. And, you know, when you think about, like, what are the capabilities that are so compelling about cloud computing, one of them is yes, what you mentioned, which is you have an idea at nine o'clock at night and swipe a credit card, and you're off and running. And that is not the case for an idea that someone has who is going to use the on-premises infrastructure of their company. And this is where you get shadow IT and 16 digits to freedom and all the like.Corey: Yeah, everyone with a corporate credit card winds up being a shadow IT source in many cases. If your processes as a company don't make it easier to proceed rather than doing it the wrong way, people are going to be fighting against you every step of the way. Sometimes the only stick you've got is that of regulation, which in some industries, great, but in other cases, no, you get to play Whack-a-Mole. I've talked to too many companies that have specific scanners built into their mail system every month looking for things that look like AWS invoices.Steve: [laugh]. Right, exactly. And so, you know, but if you flip it around, and you say, well, what if the experience for all of my infrastructure that I am running, or that I want to provide to my software development teams, be it rented through AWS, GCP, Azure, or owned for economic reasons or latency reasons, I had a similar set of characteristics where my development team could hit an API endpoint and provision instances in a matter of seconds when they had an idea and only pay for what they use, back to kind of corporate IT. And what if they were able to use the same kind of developer tools they've become accustomed to using, be it Terraform scripts and the kinds of access that they are accustomed to using? How do you make those developers just as productive across the business, instead of just through public cloud infrastructure?At that point, then you are in a much stronger position where you can say, you know, for a portion of things that are, as you pointed out, you know, more unpredictable, and where I want to leverage a bunch of additional services that a particular cloud provider has, I can rent that. And where I've got more persistent workloads or where I want a different economic profile or I need to have something in a very low latency manner to another set of services, I can own it. And that's where I think the real chasm is because today, you just don't—we take for granted the basic plumbing of cloud computing, you know? Elastic Compute, Elastic Storage, you know, networking and security services. And us in the cloud industry end up wanting to talk a lot more about exotic services and, sort of, higher-up stack capabilities. None of that basic plumbing is accessible on-prem.Corey: I also am curious as to where exactly Oxide lives in the stack because I used to build computers for myself in 2000, and it seems like having gone down that path a bit recently, yeah, that process hasn't really improved all that much. The same off-the-shelf components still exist and that's great. We always used to disparagingly call spinning hard drives as spinning rust in racks. You named the company Oxide; you're talking an awful lot about the Rust programming language in public a fair bit of the time, and I'm starting to wonder if maybe words don't mean what I thought they meant anymore. Where do you folks start and stop, exactly?Steve: Yeah, that's a good question. And when we started, we sort of thought the scope of what we were going to do and then what we were going to leverage was smaller than it has turned out to be. And by that I mean, man, over the last three years, we have hit a bunch of forks in the road where we had questions about do we take something off the shelf or do we build it ourselves. And we did not try to build everything ourselves. So, to give you a sense of kind of where the dotted line is, around the Oxide product, what we're delivering to customers is a rack-level computer. So, the minimum size comes in rack form. And I think your listeners are probably pretty familiar with this. But, you know, a rack is—Corey: You would be surprised. It's basically, what are they about seven feet tall?Steve: Yeah, about eight feet tall.Corey: Yeah, yeah. Seven, eight feet, weighs a couple 1000 pounds, you know, make an insulting joke about—Steve: Two feet wide.Corey: —NBA players here. Yeah, all kinds of these things.Steve: Yeah. And big hunk of metal. And in the cases of on-premises infrastructure, it's kind of a big hunk of metal hole, and then a bunch of 1U and 2U boxes crammed into it. What the hyperscalers have done is something very different. They started looking at, you know, at the rack level, how can you get much more dense, power-efficient designs, doing things like using a DC bus bar down the back, instead of having 64 power supplies with cables hanging all over the place in a rack, which I'm sure is what you're more familiar with.Corey: Tremendous amount of weight as well because you have the metal chassis for all of those 1U things, which in some cases, you wind up with, what, 46U in a rack, assuming you can even handle the cooling needs of all that.Steve: That's right.Corey: You have so much duplication, and so much of the weight is just metal separating one thing from the next thing down below it. And there are opportunities for massive improvement, but you need to be at a certain point of scale to get there.Steve: You do. You do. And you also have to be taking on the entire problem. You can't pick at parts of these things. And that's really what we found. So, we started at this sort of—the rack level as sort of the design principle for the product itself and found that that gave us the ability to get to the right geometry, to get as much CPU horsepower and storage and throughput and networking into that kind of chassis for the least amount of wattage required, kind of the most power-efficient design possible.So, it ships at the rack level and it ships complete with both our server sled systems in Oxide, a pair of Oxide switches. This is—when I talk about, like, design decisions, you know, do we build our own switch, it was a big, big, big question early on. We were fortunate even though we were leaning towards thinking we needed to go do that, we had this prospective early investor who was early at AWS and he had asked a very tough question that none of our other investors had asked to this point, which is, “What are you going to do about the switch?”And we knew that the right answer to an investor is like, “No. We're already taking on too much.” We're redesigning a server from scratch in, kind of, the mold of what some of the hyperscalers have learned, doing our own Root of Trust, we're doing our own operating system, hypervisor control plane, et cetera. Taking on the switch could be seen as too much, but we told them, you know, we think that to be able to pull through all of the value of the security benefits and the performance and observability benefits, we can't have then this [laugh], like, obscure third-party switch rammed into this rack.Corey: It's one of those things that people don't think about, but it's the magic of cloud with AWS's network, for example, it's magic. You can get line rate—or damn near it—between any two points, sustained.Steve: That's right.Corey: Try that in the data center, you wind into massive congestion with top-of-rack switches, where, okay, we're going to parallelize this stuff out over, you know, two dozen racks and we're all going to have them seamlessly transfer information between each other at line rate. It's like, “[laugh] no, you're not because those top-of-rack switches will melt and become side-of-rack switches, and then bottom-puddle-of-rack switches. It doesn't work that way.”Steve: That's right.Corey: And you have to put a lot of thought and planning into it. That is something that I've not heard a traditional networking vendor addressing because everyone loves to hand-wave over it.Steve: Well so, and this particular prospective investor, we told him, “We think we have to go build our own switch.” And he said, “Great.” And we said, “You know, we think we're going to lose you as an investor as a result, but this is what we're doing.” And he said, “If you're building your own switch, I want to invest.” And his comment really stuck with us, which is AWS did not stand on their own two feet until they threw out their proprietary switch vendor and built their own.And that really unlocked, like you've just mentioned, like, their ability, both in hardware and software to tune and optimize to deliver that kind of line rate capability. And that is one of the big findings for us as we got into it. Yes, it was really, really hard, but based on a couple of design decisions, P4 being the programming language that we are using as the surround for our silicon, tons of opportunities opened up for us to be able to do similar kinds of optimization and observability. And that has been a big, big win.But to your question of, like, where does it stop? So, we are delivering this complete with a baked-in operating system, hypervisor, control plane. And so, the endpoint of the system, where the customer meets is either hitting an API or a CLI or a console that delivers and kind of gives you the ability to spin up projects. And, you know, if one is familiar with EC2 and EBS and VPC, that VM level of abstraction is where we stop.Corey: That, I think, is a fair way of thinking about it. And a lot of cloud folks are going to pooh-pooh it as far as saying, “Oh well, just virtual machines. That's old cloud. That just treats the cloud like a data center.” And in many cases, yes, it does because there are ways to build modern architectures that are event-driven on top of things like Lambda, and API Gateway, and the rest, but you take a look at what my customers are doing and what drives the spend, it is invariably virtual machines that are largely persistent.Sometimes they scale up, sometimes they scale down, but there's always a baseline level of load that people like to hand-wave away the fact that what they're fundamentally doing in a lot of these cases, is paying the cloud provider to handle the care and feeding of those systems, which can be expensive, yes, but also delivers significant innovation beyond what almost any company is going to be able to deliver in-house. There is no way around it. AWS is better than you are—whoever you happen to—be at replacing failed hard drives. That is a simple fact. They have teams of people who are the best in the world of replacing failed hard drives. You generally do not. They are going to be better at that than you. But that's not the only axis. There's not one calculus that leads to, is cloud a scam or is cloud a great value proposition for us? The answer is always a deeply nuanced, “It depends.”Steve: Yeah, I mean, I think cloud is a great value proposition for most and a growing amount of software that's being developed and deployed and operated. And I think, you know, one of the myths that is out there is, hey, turn over your IT to AWS because we have or you know, a cloud provider—because we have such higher caliber personnel that are really good at swapping hard drives and dealing with networks and operationally keeping this thing running in a highly available manner that delivers good performance. That is certainly true, but a lot of the operational value in an AWS is been delivered via software, the automation, the observability, and not actual people putting hands on things. And it's an important point because that's been a big part of what we're building into the product. You know, just because you're running infrastructure in your own data center, it does not mean that you should have to spend, you know, 1000 hours a month across a big team to maintain and operate it. And so, part of that, kind of, cloud, hyperscaler innovation that we're baking into this product is so that it is easier to operate with much, much, much lower overhead in a highly available, resilient manner.Corey: So, I've worked in a number of data center facilities, but the companies I was working with, were always at a scale where these were co-locations, where they would, in some cases, rent out a rack or two, in other cases, they'd rent out a cage and fill it with their own racks. They didn't own the facilities themselves. Those were always handled by other companies. So, my question for you is, if I want to get a pile of Oxide racks into my environment in a data center, what has to change? What are the expectations?I mean, yes, there's obviously going to be power and requirements at the data center colocation is very conversant with, but Open Compute, for example, had very specific requirements—to my understanding—around things like the airflow construction of the environment that they're placed within. How prescriptive is what you've built, in terms of doing a building retrofit to start using you folks?Steve: Yeah, definitely not. And this was one of the tensions that we had to balance as we were designing the product. For all of the benefits of hyperscaler computing, some of the design center for you know, the kinds of racks that run in Google and Amazon and elsewhere are hyperscaler-focused, which is unlimited power, in some cases, data centers designed around the equipment itself. And where we were headed, which was basically making hyperscaler infrastructure available to, kind of, the masses, the rest of the market, these folks don't have unlimited power and they aren't going to go be able to go redesign data centers. And so no, the experience should be—with exceptions for folks maybe that have very, very limited access to power—that you roll this rack into your existing data center. It's on standard floor tile, that you give it power, and give it networking and go.And we've spent a lot of time thinking about how we can operate in the wide-ranging environmental characteristics that are commonplace in data centers that focus on themselves, colo facilities, and the like. So, that's really on us so that the customer is not having to go to much work at all to kind of prepare and be ready for it.Corey: One of the challenges I have is how to think about what you've done because you are rack-sized. But what that means is that my own experimentation at home recently with on-prem stuff for smart home stuff involves a bunch of Raspberries Pi and a [unintelligible 00:19:42], but I tend to more or less categorize you the same way that I do AWS Outposts, as well as mythical creatures, like unicorns or giraffes, where I don't believe that all these things actually exist because I haven't seen them. And in fact, to get them in my house, all four of those things would theoretically require a loading dock if they existed, and that's a hard thing to fake on a demo signup form, as it turns out. How vaporware is what you've built? Is this all on paper and you're telling amazing stories or do they exist in the wild?Steve: So, last time we were on, it was all vaporware. It was a couple of napkin drawings and a seed round of funding.Corey: I do recall you not using that description at the time, for what it's worth. Good job.Steve: [laugh]. Yeah, well, at least we were transparent where we were going through the race. We had some napkin drawings and we had some good ideas—we thought—and—Corey: You formalize those and that's called Microsoft PowerPoint.Steve: That's it. A hundred percent.Corey: The next generative AI play is take the scrunched-up, stained napkin drawing, take a picture of it, and convert it to a slide.Steve: Google Docs, you know, one of those. But no, it's got a lot of scars from the build and it is real. In fact, next week, we are going to be shipping our first commercial systems. So, we have got a line of racks out in our manufacturing facility in lovely Rochester, Minnesota. Fun fact: Rochester, Minnesota, is where the IBM AS/400s were built.Corey: I used to work in that market, of all things.Steve: Really?Corey: Selling tape drives in the AS/400. I mean, I still maintain there's no real mainframe migration to the cloud play because there's no AWS/400. A joke that tends to sail over an awful lot of people's heads because, you know, most people aren't as miserable in their career choices as I am.Steve: Okay, that reminds me. So, when we were originally pitching Oxide and we were fundraising, we [laugh]—in a particular investor meeting, they asked, you know, “What would be a good comp? Like how should we think about what you are doing?” And fortunately, we had about 20 investor meetings to go through, so burning one on this was probably okay, but we may have used the AS/400 as a comp, talking about how [laugh] mainframe systems did such a good job of building hardware and software together. And as you can imagine, there were some blank stares in that room.But you know, there are some good analogs to historically in the computing industry, when you know, the industry, the major players in the industry, were thinking about how to deliver holistic systems to support end customers. And, you know, we see this in the what Apple has done with the iPhone, and you're seeing this as a lot of stuff in the automotive industry is being pulled in-house. I was listening to a good podcast. Jim Farley from Ford was talking about how the automotive industry historically outsourced all of the software that controls cars, right? So, like, Bosch would write the software for the controls for your seats.And they had all these suppliers that were writing the software, and what it meant was that innovation was not possible because you'd have to go out to suppliers to get software changes for any little change you wanted to make. And in the computing industry, in the 80s, you saw this blow apart where, like, firmware got outsourced. In the IBM and the clones, kind of, race, everyone started outsourcing firmware and outsourcing software. Microsoft started taking over operating systems. And then VMware emerged and was doing a virtualization layer.And this, kind of, fragmented ecosystem is the landscape today that every single on-premises infrastructure operator has to struggle with. It's a kit car. And so, pulling it back together, designing things in a vertically integrated manner is what the hyperscalers have done. And so, you mentioned Outposts. And, like, it's a good example of—I mean, the most public cloud of public cloud companies created a way for folks to get their system on-prem.I mean, if you need anything to underscore the draw and the demand for cloud computing-like, infrastructure on-prem, just the fact that that emerged at all tells you that there is this big need. Because you've got, you know, I don't know, a trillion dollars worth of IT infrastructure out there and you have maybe 10% of it in the public cloud. And that's up from 5% when Jassy was on stage in '21, talking about 95% of stuff living outside of AWS, but there's going to be a giant market of customers that need to own and operate infrastructure. And again, things have not improved much in the last 10 or 20 years for them.Corey: They have taken a tone onstage about how, “Oh, those workloads that aren't in the cloud, yet, yeah, those people are legacy idiots.” And I don't buy that for a second because believe it or not—I know that this cuts against what people commonly believe in public—but company execs are generally not morons, and they make decisions with context and constraints that we don't see. Things are the way they are for a reason. And I promise that 90% of corporate IT workloads that still live on-prem are not being managed or run by people who've never heard of the cloud. There was a decision made when some other things were migrating of, do we move this thing to the cloud or don't we? And the answer at the time was no, we're going to keep this thing on-prem where it is now for a variety of reasons of varying validity. But I don't view that as a bug. I also, frankly, don't want to live in a world where all the computers are basically run by three different companies.Steve: You're spot on, which is, like, it does a total disservice to these smart and forward-thinking teams in every one of the Fortune 1000-plus companies who are taking the constraints that they have—and some of those constraints are not monetary or entirely workload-based. If you want to flip it around, we were talking to a large cloud SaaS company and their reason for wanting to extend it beyond the public cloud is because they want to improve latency for their e-commerce platform. And navigating their way through the complex layers of the networking stack at GCP to get to where the customer assets are that are in colo facilities, adds lag time on the platform that can cost them hundreds of millions of dollars. And so, we need to think behind this notion of, like, “Oh, well, the dark ages are for software that can't run in the cloud, and that's on-prem. And it's just a matter of time until everything moves to the cloud.”In the forward-thinking models of public cloud, it should be both. I mean, you should have a consistent experience, from a certain level of the stack down, everywhere. And then it's like, do I want to rent or do I want to own for this particular use case? In my vast set of infrastructure needs, do I want this to run in a data center that Amazon runs or do I want this to run in a facility that is close to this other provider of mine? And I think that's best for all. And then it's not this kind of false dichotomy of quality infrastructure or ownership.Corey: I find that there are also workloads where people will come to me and say, “Well, we don't think this is going to be economical in the cloud”—because again, I focus on AWS bills. That is the lens I view things through, and—“The AWS sales rep says it will be. What do you think?” And I look at what they're doing and especially if involves high volumes of data transfer, I laugh a good hearty laugh and say, “Yeah, keep that thing in the data center where it is right now. You will thank me for it later.”It's, “Well, can we run this in an economical way in AWS?” As long as you're okay with economical meaning six times what you're paying a year right now for the same thing, yeah, you can. I wouldn't recommend it. And the numbers sort of speak for themselves. But it's not just an economic play.There's also the story of, does this increase their capability? Does it let them move faster toward their business goals? And in a lot of cases, the answer is no, it doesn't. It's one of those business process things that has to exist for a variety of reasons. You don't get to reimagine it for funsies and even if you did, it doesn't advance the company in what they're trying to do any, so focus on something that differentiates as opposed to this thing that you're stuck on.Steve: That's right. And what we see today is, it is easy to be in that mindset of running things on-premises is kind of backwards-facing because the experience of it is today still very, very difficult. I mean, talking to folks and they're sharing with us that it takes a hundred days from the time all the different boxes land in their warehouse to actually having usable infrastructure that developers can use. And our goal and what we intend to go hit with Oxide as you can roll in this complete rack-level system, plug it in, within an hour, you have developers that are accessing cloud-like services out of the infrastructure. And that—God, countless stories of firmware bugs that would send all the fans in the data center nonlinear and soak up 100 kW of power.Corey: Oh, God. And the problems that you had with the out-of-band management systems. For a long time, I thought Drax stood for, “Dell, RMA Another Computer.” It was awful having to deal with those things. There was so much room for innovation in that space, which no one really grabbed onto.Steve: There was a really, really interesting talk at DEFCON that we just stumbled upon yesterday. The NVIDIA folks are giving a talk on BMC exploits… and like, a very, very serious BMC exploit. And again, it's what most people don't know is, like, first of all, the BMC, the Baseboard Management Controller, is like the brainstem of the computer. It has access to—it's a backdoor into all of your infrastructure. It's a computer inside a computer and it's got software and hardware that your server OEM didn't build and doesn't understand very well.And firmware is even worse because you know, firmware written by you know, an American Megatrends or other is a big blob of software that gets loaded into these systems that is very hard to audit and very hard to ascertain what's happening. And it's no surprise when, you know, back when we were running all the data centers at a cloud computing company, that you'd run into these issues, and you'd go to the server OEM and they'd kind of throw their hands up. Well, first they'd gaslight you and say, “We've never seen this problem before,” but when you thought you've root-caused something down to firmware, it was anyone's guess. And this is kind of the current condition today. And back to, like, the journey to get here, we kind of realized that you had to blow away that old extant firmware layer, and we rewrote our own firmware in Rust. Yes [laugh], I've done a lot in Rust.Corey: No, it was in Rust, but, on some level, that's what Nitro is, as best I can tell, on the AWS side. But it turns out that you don't tend to have the same resources as a one-and-a-quarter—at the moment—trillion-dollar company. That keeps [valuing 00:30:53]. At one point, they lost a comma and that was sad and broke all my logic for that and I haven't fixed it since. Unfortunate stuff.Steve: Totally. I think that was another, kind of, question early on from certainly a lot of investors was like, “Hey, how are you going to pull this off with a smaller team and there's a lot of surface area here?” Certainly a reasonable question. Definitely was hard. The one advantage—among others—is, when you are designing something kind of in a vertical holistic manner, those design integration points are narrowed down to just your equipment.And when someone's writing firmware, when AMI is writing firmware, they're trying to do it to cover hundreds and hundreds of components across dozens and dozens of vendors. And we have the advantage of having this, like, purpose-built system, kind of, end-to-end from the lowest level from first boot instruction, all the way up through the control plane and from rack to switch to server. That definitely helped narrow the scope.Corey: This episode has been fake sponsored by our friends at AWS with the following message: Graviton Graviton, Graviton, Graviton, Graviton, Graviton, Graviton, Graviton, Graviton. Thank you for your l-, lack of support for this show. Now, AWS has been talking about Graviton an awful lot, which is their custom in-house ARM processor. Apple moved over to ARM and instead of talking about benchmarks they won't publish and marketing campaigns with words that don't mean anything, they've let the results speak for themselves. In time, I found that almost all of my workloads have moved over to ARM architecture for a variety of reason, and my laptop now gets 15 hours of battery life when all is said and done. You're building these things on top of x86. What is the deal there? I do not accept that if that you hadn't heard of ARM until just now because, as mentioned, Graviton, Graviton, Graviton.Steve: That's right. Well, so why x86, to start? And I say to start because we have just launched our first generation products. And our first-generation or second-generation products that we are now underway working on are going to be x86 as well. We've built this system on AMD Milan silicon; we are going to be launching a Genoa sled.But when you're thinking about what silicon to use, obviously, there's a bunch of parts that go into the decision. You're looking at the kind of applicability to workload, performance, power management, for sure, and if you carve up what you are trying to achieve, x86 is still a terrific fit for the broadest set of workloads that our customers are trying to solve for. And choosing which x86 architecture was certainly an easier choice, come 2019. At this point, AMD had made a bunch of improvements in performance and energy efficiency in the chip itself. We've looked at other architectures and I think as we are incorporating those in the future roadmap, it's just going to be a question of what are you trying to solve for.You mentioned power management, and that is kind of commonly been a, you know, low power systems is where folks have gone beyond x86. Is we're looking forward to hardware acceleration products and future products, we'll certainly look beyond x86, but x86 has a long, long road to go. It still is kind of the foundation for what, again, is a general-purpose cloud infrastructure for being able to slice and dice for a variety of workloads.Corey: True. I have to look around my environment and realize that Intel is not going anywhere. And that's not just an insult to their lack of progress on committed roadmaps that they consistently miss. But—Steve: [sigh].Corey: Enough on that particular topic because we want to keep this, you know, polite.Steve: Intel has definitely had some struggles for sure. They're very public ones, I think. We were really excited and continue to be very excited about their Tofino silicon line. And this came by way of the Barefoot networks acquisition. I don't know how much you had paid attention to Tofino, but what was really, really compelling about Tofino is the focus on both hardware and software and programmability.So, great chip. And P4 is the programming language that surrounds that. And we have gotten very, very deep on P4, and that is some of the best tech to come out of Intel lately. But from a core silicon perspective for the rack, we went with AMD. And again, that was a pretty straightforward decision at the time. And we're planning on having this anchored around AMD silicon for a while now.Corey: One last question I have before we wind up calling it an episode, it seems—at least as of this recording, it's still embargoed, but we're not releasing this until that winds up changing—you folks have just raised another round, which means that your napkin doodles have apparently drawn more folks in, and now that you're shipping, you're also not just bringing in customers, but also additional investor money. Tell me about that.Steve: Yes, we just completed our Series A. So, when we last spoke three years ago, we had just raised our seed and had raised $20 million at the time, and we had expected that it was going to take about that to be able to build the team and build the product and be able to get to market, and [unintelligible 00:36:14] tons of technical risk along the way. I mean, there was technical risk up and down the stack around this [De Novo 00:36:21] server design, this the switch design. And software is still the kind of disproportionate majority of what this product is, from hypervisor up through kind of control plane, the cloud services, et cetera. So—Corey: We just view it as software with a really, really confusing hardware dongle.Steve: [laugh]. Yeah. Yes.Corey: Super heavy. We're talking enterprise and government-grade here.Steve: That's right. There's a lot of software to write. And so, we had a bunch of milestones that as we got through them, one of the big ones was getting Milan silicon booting on our firmware. It was funny it was—this was the thing that clearly, like, the industry was most suspicious of, us doing our own firmware, and you could see it when we demonstrated booting this, like, a year-and-a-half ago, and AMD all of a sudden just lit up, from kind of arm's length to, like, “How can we help? This is amazing.” You know? And they could start to see the benefits of when you can tie low-level silicon intelligence up through a hypervisor there's just—Corey: No I love the existing firmware I have. Looks like it was written in 1984 and winds up having terrible user ergonomics that hasn't been updated at all, and every time something comes through, it's a 50/50 shot as whether it fries the box or not. Yeah. No, I want that.Steve: That's right. And you look at these hyperscale data centers, and it's like, no. I mean, you've got intelligence from that first boot instruction through a Root of Trust, up through the software of the hyperscaler, and up to the user level. And so, as we were going through and kind of knocking down each one of these layers of the stack, doing our own firmware, doing our own hardware Root of Trust, getting that all the way plumbed up into the hypervisor and the control plane, number one on the customer side, folks moved from, “This is really interesting. We need to figure out how we can bring cloud capabilities to our data centers. Talk to us when you have something,” to, “Okay. We actually”—back to the earlier question on vaporware, you know, it was great having customers out here to Emeryville where they can put their hands on the rack and they can, you know, put your hands on software, but being able to, like, look at real running software and that end cloud experience.And that led to getting our first couple of commercial contracts. So, we've got some great first customers, including a large department of the government, of the federal government, and a leading firm on Wall Street that we're going to be shipping systems to in a matter of weeks. And as you can imagine, along with that, that drew a bunch of renewed interest from the investor community. Certainly, a different climate today than it was back in 2019, but what was great to see is, you still have great investors that understand the importance of making bets in the hard tech space and in companies that are looking to reinvent certain industries. And so, we added—our existing investors all participated. We added a bunch of terrific new investors, both strategic and institutional.And you know, this capital is going to be super important now that we are headed into market and we are beginning to scale up the business and make sure that we have a long road to go. And of course, maybe as importantly, this was a real confidence boost for our customers. They're excited to see that Oxide is going to be around for a long time and that they can invest in this technology as an important part of their infrastructure strategy.Corey: I really want to thank you for taking the time to speak with me about, well, how far you've come in a few years. If people want to learn more and have the requisite loading dock, where should they go to find you?Steve: So, we try to put everything up on the site. So, oxidecomputer.com or oxide.computer. We also, if you remember, we did [On the Metal 00:40:07]. So, we had a Tales from the Hardware-Software Interface podcast that we did when we started. We have shifted that to Oxide and Friends, which the shift there is we're spending a little bit more time talking about the guts of what we built and why. So, if folks are interested in, like, why the heck did you build a switch and what does it look like to build a switch, we actually go to depth on that. And you know, what does bring-up on a new server motherboard look like? And it's got some episodes out there that might be worth checking out.Corey: We will definitely include a link to that in the [show notes 00:40:36]. Thank you so much for your time. I really appreciate it.Steve: Yeah, Corey. Thanks for having me on.Corey: Steve Tuck, CEO at Oxide Computer Company. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this episode, please leave a five-star review on your podcast platform of choice, along with an angry ranting comment because you are in fact a zoology major, and you're telling me that some animals do in fact exist. But I'm pretty sure of the two of them, it's the unicorn.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Histoire vivante poursuit sa série sur les conséquences du génocide des Arméniens en 1915. Dans les années qui suivent la Première guerre mondiale, les massacres de masse des Arméniens sont dilués dans un bilan global écrasant. On ne leur rend pas justice et ils perdent définitivement leur droit au retour après le Traité de Lausanne en 1923. Pourtant un évènement fait date dans ce début des années 1920, le procès de Soghomon Tehlirian. Ce jeune Arménien tue dʹune balle de revolver dans une rue de Berlin un certain Talaat Pacha, le 15 mars 1921. Son procès, deux mois plus tard, est lʹoccasion de raconter au grand public le génocide et lʹabsence de justice réelle rendue aux victimes. Au cours de ces journées de juin 1921 la responsabilité de la victime dans le génocide des Arméniens devient lʹobjet central de toutes les attentions. Cʹest Rafael Lemkin, qui invente le mot génocide et sa définition juridique un peu plus de vingt ans plus tard alors que lʹextermination des Juifs dʹEurope est en cours. Un mot forgé aussi à partir du procès Tehlirian quʹil avait suivi avec grand intérêt alors quʹil était étudiant en droit. Avec Sévane Garibian, directrice de lʹouvrage La mort du bourreau : réflexions interdisciplinaires sur le cadavre des criminels de masse, Editions Petra, Vicken Cheterian, auteur du livre Open Wounds, Hurst and Oxford University Press, Anouche Kunth, autrice dʹAu bord de lʹeffacement. Sur les pas d'exilés arméniens dans l'entre-deux-guerres, La Découverte et Annette Becker " Raphael Lemkin, lʹextermination des Arméniens et lʹinvention du mot génocide ", in LʹExtermination des Arméniens de lʹEmpire ottoman. Une série dʹAnaïs Kien Retrouvez toutes les séries dʹHistoire Vivante sur rts.ch/audio Histoire Vivante cʹest aussi tous les vendredis dans les pages de La Liberté et sur RTS 2, le dimanche soir.