Podcasts about cpu

Send us a textARM Ascends, Oil Drifts, Queens EnduresI open on macro static and shutdown fog, a strange steadiness where the market beat goes on. The Beige Book whispers fractures, three Fed districts up, five flat, four softening, a recalibration more than a roar. The feature turns to ARM, where the data center bottleneck is power, not code. ARM sells the blueprint, cutting CPU energy use perhaps by half, and the live question is simple: can it win 50 percent of data center CPUs. Then energy's riddle: oil sits near $56, where it was in 2005, with about 1.5 trillion barrels of proven reserves setting the rough scale. I close with Queens County, a Tony Soprano thrift that became my acid test and first great trade, the name fades, but the fuse remains.If this hit the mark, tap 5 

We're back for Episode 164 of Pixel Gaiden! In this episode Cody and Eric catch up on the news and cover Battle Of The Systems: Night Slashers (Arcade, Data East) vs Metamorphic Force (Arcade, Konami)   7:12 - Quick Questions 33:19 - Patreon Song 36:58- Tea Time With Tim - Amiga Memories 49:45 - Cody's Corner - Cool Systems To Collect For 1:07:38 - News 2:01:24- Battle Of The Systems: Night Slashers (Arcade, Data East) vs Metamorphic Force (Arcade, Konami)   News -    Cody – A full sized modern Amiga? https://www.timeextension.com/news/2025/09/amiga-lives-apollo-a6000-promises-to-pick-up-where-commodore-left-off  Tim – Could this be the best Amiga ever?  – NEW... Raspberry Pi 500+ quad-core 64-bit Arm, CPU, 16Gb RAM, 256GB NVMe SSD included. Plus, a new mechanical keyboard with coloured LED's. Ideal for use with PiMiga to give the ultimate Amiga in a very small footprint.  https://www.raspberrypi.com/products/raspberry-pi-500-plus/  Cody – Playdate now has Folders!   Is this a big deal Eric? https://www.timeextension.com/news/2025/10/playdate-os-3-0-adds-a-much-requested-feature-folders   Tim - RM 800XL – Atari 800XL modern recreation in the offing from Revive Machines in Poland. The website is dated 2023, so not sure what the progress is. This came from something on my Bluesky feed showing the case mockup. Looks promising here are the details so far on the site:  https://revive-machines.com/index-en.html  Cody – Lets bust out the NeoGeo Pocket! https://www.timeextension.com/news/2025/10/dont-die-mr-robot-gets-demade-for-the-neo-geo-pocket-color   Eric - New Baldur's Gate 3 Update Includes Steam Deck-Native Version Of The RPG – GameSpot  https://www.gamespot.com/articles/new-baldurs-gate-3-hotfix-includes-steam-deck-native-version-of-the-rpg/1100-6534954/   Cody – I have always wanted to play these star wars games, now I can? https://www.timeextension.com/news/2025/09/these-new-snes-rom-hacks-aim-to-make-the-super-star-wars-trilogy-a-whole-lot-fairer  Tim – New Arcade Archive games come to consoles. Master of Weapon, Growl, Fighting Hawk, Crime City and more..  10 More Arcade Archives Games From Taito Are 30% Off Right Now   Cody – ASCII Art Lovers Might Enjoy this one  https://www.retronews.com/effulgence-rpg-steam/  Eric - Dreamcast Arcade Romp Shadow Gangs Gets Reprint - Retro News  https://www.retronews.com/shadow-gangs-reprint/  Cody – A new virtual Boy...kinda.  https://www.nintendolife.com/news/2025/09/icymi-if-you-want-to-play-virtual-boy-classics-youll-need-to-buy-one-of-nintendos-accessories  Tim – New Lego Gameboy, out now (when this is released!)  https://www.lego.com/en-gb/product/game-boy-72046  Cody – New Halloween Game for October? https://www.retronews.com/halloween-1985-next-month/  Eric - Rayman Leaps Back Onto GBC With New Chromatic Release - Retro News  https://www.retronews.com/rayman-leaps-onto-gbc/  Cody – “MegaVania?”  Now that is my kinda game! https://www.timeextension.com/news/2025/09/castlevania-inspired-spine-lasher-is-a-megavania-not-a-metroidvania  Eric - Now in orange!!!  https://www.timeextension.com/news/2025/09/8bitdo-is-releasing-its-pro-3-in-spice-orange-to-match-your-beloved-gamecube   Cody – Pretty cool new C64 Title  https://www.indieretronews.com/2025/09/death-sector-rather-decent-sci-fi.html#more   News of the weird - https://www.timeextension.com/news/2025/09/random-c64-and-spectrum-fragrances-are-coming-this-christmas-and-they-dont-smell-like-body-odour-and-sweaty-socks  https://retrododo.com/campbells-team-up-with-pokemon-for-a-competition-to-soup-up-your-game-room/    Please give us a review on Apple Podcasts! Thanks for listening! You can always reach us at podcast@pixelgaiden.com. Send us an email if we missed anything in the show notes you need. You can now support us on Patreon.  Thank you to Roy Fielding, Daniel James, 10MARC, Eric Sandgren, Brian Arsenault, Retro Gamer Nation, Maciej Sosnowski, Paradroyd, RAM OK ROM OK, Mitsoyama, David Vincent, Ant Stiller, Mr. Toast, Jason Holland, Mark Scott, Vicky Lamburn, Mark Richardson, Scott Partelow, Paul Jacobson, Steve Rasmussen, Steve Rasmussen's Mom, Retro Gamer Nation, Peter Price, Brett Alexander, Jason Warnes, Josh Malone (48kram), AndrewSan, Joe Ochwat, John Shawler, and Adam from Commodore Chronicles for making this show possible through their generous donation to the show.

On October 9, 2025, the ACOG released a clinical practice update (CPU) regarding Zouranolone and brexanolone. As postpartum depression is an area of continued research and need for therapeutics, any new clinical practice update on the subject is welcome. So what's new in this update?! Well…the answer will surprise you. Listen in for details on the CPU, and a mini-review of the concerns for Zuranolone. 1. ACOG CPU Oct 9, 2025: Zuranolone and Brexanolone for the Treatment of Postpartum Depression 2. ACOG PA Aug 2023: Zuranolone for the Treatment of Postpartum Depression 3. Clinical Practice Guideline No. 5, Treatment and Management of Mental Health Conditions During Pregnancy and Postpartum (Obstet Gynecol 2023;141:1262–88)STRONG COFFEE PROMO: 20% Off Strong Coffee Company https://strongcoffeecompany.com/discount/CHAPANOSPINOBG

Jeremy and Brett could not make it (not to be confused with renowned British actor Jeremy Brett), but the show must go on! A shorter, and probably worse version, but a version nonetheless.  Some topics still got covered though!Timestamps:00:00 Intro01:18 Patreon02:24 Food with Josh04:18 AMD partners with OpenAI, offers 10% of the company16:14 NVIDIA partners with xAI17:07 Qualcomm acquires Arduino18:37 Synology drops self-branded HDD requirement20:44 be quiet! expands Light Base case lineup22:01 Help us OOBE Wan Kenobi, local accounts are our only hope24:17 MSI says their 800 Series boards are future CPU ready29:46 (In)Security Corner minus Jeremy and Brett36:15 Gaming Quick Hits45:58 Picks of the Week53:51 Outro ★ Support this podcast on Patreon ★

Hello and welcome to Handgun Radio! I'm your host Ryan Michad, Weerd Beard & Co from the wild woods of Central Maine and this is your home for all the news, information and discussion in the handgunning world!   This week, we talk listener entries for the rebuilding your collection episode!   Please check out the Patriot Patch Company for their awesome patches and other high quality  items! Visit www.patriotpatch.co for more information! Cool artist “proof” rendition come along with the latest patch of the month patches!    We are proudly sponsored by VZ Grips! Please go check out all their fantastic products at their website! VZ Grips!  -KFrame Magna Grips   Thank you to all our patreons! Visit us at https://www.patreon.com/handgunradio    Week In Review:    Ryan:  - I didnt do much; geeked out over the Rideout Arsenal episode that just posted! -Checked out T&K Arms in Augusta! A nice, clean, well setup shop that had two friendly Bernese Mountain Dogs to greet the customers! -Found my geek book: What If? Alternate History Timelines. -Robert Redford passes. My favorite movies: Three Days of The Condor; All The Presidents Men; Spy Game   David: Rosh Hashanah started this week. Lots of time at temple Watched Spinal Tap with the kids 3D Print commission, obdurator disks for MadMikes 81mm Mortar Septic issue resolved. New drain field dug.   Oddball: 9mm AR pistol featuring a Stern Defense mag adapter Installed new motherboard, CPU, and RAM in gaming rig   Weerd:   Drink Segment:   Vemont Ice Gin George Dickel 8-year Bourbon  Adjusted Cosmopolitan Food Segment: Aioli Garden Watermelon Rosh Hashannah Challah   Main Topic: Rebuilding Entries   —------------ Listener Myles:   Hi Ryan,   As for my budget rebuild this would be my start.   Building on a budget   Ruger redhawk 4.2” $1399 Ruger mkiv 22/45 $449 Canik mc9 prime $619 optic $300 upgrade from mc9 Canik rival dark side with optic $849 Beretta bobcat $549   Total about $3800 so a little ammo to go with it along with holsters.   —-------------------------------------------------------    Listener Phil:   Hello from the beautiful southwest!   So, I've lost my precious gun collection but got $5,000USD to replace it.  I go to Buds and find an MR-73 with 4” barrel, $3995.   Thank you for your time, you've been great, goodnight everybody!   Well we like options so depending on wind direction, etc maybe this-   Buds again and buy a Colt Commander and a Defender. $900 each. Swap slides and keep the CCO and sell the other one on Gunbroker for about $650.  Buy a S&W .357 4” (19,65 whatever) about $850.    Buy a S&W big bore snub (625,629 whatever) about $900.   So, I'm at $2,150 and GunBroker has the S&W 4506 available for about $1,300 for my hipster want.   Then back to Buds to wrap things up with a S&W Bodyguard 2.0 and a S&W 642 for all my pocket carry needs.  $400 and $450, they zero me out.   But really, if I have nothing but $5K in my hand? MR-73 and all the ammo and cool ass holsters I can think up seems pretty irresistible.   —--------------------------------------------------------------------------------------------------   Listener R:   Ruger Mark IV 22/45 .22LR 4.4" 10rd Pistol, Black - 40190 $330 on buds   TAURUS TX22 $235 on guns.com   S&W Model 460 XVR 8.38" .460 S&W Revolver $1130 on GunBroker   THE NEW THOMPSON CENTER STAINLESS ENCORE/PROHUNTER PISTOL FRAME ONLY $400 on hausofarms   Rost Martin RM1C Black 9mm 4" Barrel 15-Rounds Package $450 grab gun   Hi-Point JXP-10 10mm Pistol 5.2" Threaded Barrel 10rd, Black - JXP10 $166 buds gun shop   $350 ish see some cheaper on buds but all I have had is rock Island tisas girsan that have worked never tried Taylor's and Co or GeForce   

Surya, a tech historian, buys an old Sun workstation at a garage sale, expecting a working example of a CPU her grandmother designed, not secrets. Accidentally left on the drive are two files of NASA's lost Voyager 2 data. When she attempts to learn about the workstation's history by contacting a name she discovers in one of the files, she attracts unwanted attention: break-ins, shadowy men, and veiled threats. She eventually tracks down Mark Danforth, a retired engineer now fading into dementia, who may hold the key. But someone will do anything to keep the files she has discovered buried. CONNECT WITH US makeshiftstories@gmail.com SHARE THE PODCAST If you liked this episode, tell your friends to head over to Apple Podcasts and subscribe. CREDITS Written by Vern Hume (AKA Alan V Hare). Read by Kathleen Connelly. Opening and closing were composed and created by Matthew Erdmann. Produced by Vecada Studios. Makeshift Stories is released under a creative commons non-commercial attribution, no derivative license.

Timestamps: 0:00 hit the 'Links with some bros 0:15 Windows 7 'market share' spike 2:02 OpenAI's new 'Sora' video slop app 3:31 Meta training on AI chat data 4:17 Gemini for Home, Nothing AI app store 5:05 War Thunder! 5:47 QUICK BITS INTRO 5:57 UK demands Apple backdoor again 6:49 Xbox Game Pass price hike, 1440p cloud gaming 7:37 Qualcomm wins against Arm again in court 8:12 new Intel Arc drivers help CPU overhead issue 8:57 Charlotte home-building spider robot NEWS SOURCES: https://lmg.gg/plguB Learn more about your ad choices. Visit megaphone.fm/adchoices

¡Apple sorprendido! Se filtra el iPad Pro M5 antes de su anuncio oficial. En este episodio te contamos todos los detalles sobre el nuevo iPad Pro M5, los cambios respecto al M4, benchmarks, batería, RAM, diferencias gráficas ¡y analizamos lo que implican para el futuro de la gama Pro! NUEVO iPAD PRO M5 FILTRADO ANTES DE SU PRESENTACIÓN ✅ Unboxing completo del iPad Pro M5 antes que Apple ✅ iPadOS 26 preinstalado ✅ Chip Apple Silicon M5 de nueva generación ✅ Más RAM en modelos base: ahora 12GB ✅ Mejora en benchmarks: +10% mono-núcleo, +15% multi-núcleo ✅ Gráficos un 34% mejores en Metal ✅ ¿Sin cambios de diseño? Solo detallitos en la trasera ✅ ¿Pequeña actualización o salto importante en el ecosistema Pro? COMPARATIVA iPAD PRO M4 VS M5 Batería fabricada en agosto 2025 ⚡ CPU de 4.42 GHz (vs 4.41 GHz en M4) Misma estética, ¿nuevo corazón? AnTuTu: +8% en potencia gráfica respecto al M4 ¿Todos los modelos con más RAM o solo los base? LÍNEA DE TIEMPO (EPISODIO DE 1 HORA): 00:00 Introducción y contexto 10:00 Unboxing, primeras impresiones y credibilidad 20:00 Detalles técnicos chip M5, RAM, diseño 28:00 iPadOS 26 y experiencia de usuario 36:00 Resultados benchmarks (Geekbench, AnTuTu, Metal) 42:00 Impacto en creatividad, productividad y gaming 48:00 Opinión Applelianos: ¿merece la pena este M5? 53:00 Rumores lanzamiento, precios y futuro gama Pro 57:00 Preguntas de la audiencia y cierre PARTICIPA EN DIRECTO Deja tu opinión en los comentarios, haz preguntas y sé parte de la charla más importante sobre el futuro del iPad y del ecosistema Apple. ¡Tu voz cuenta! ¿TE GUSTÓ EL EPISODIO? ✨ Dale LIKE SUSCRÍBETE y activa la campanita para no perderte nada COMENTA qué mejora del iPad Pro M5 te parece más relevante COMPARTE con tus amigos applelianos SÍGUENOS EN TODAS NUESTRAS PLATAFORMAS: YouTube: Applelianos Podcast Telegram: https://t.me/+Jm8IE4n3xtI2Zjdk X (Twitter): @ApplelianosPod Facebook: facebook.com/applelianos Apple Podcasts: Applelianos Podcast PATROCINADO POR SEOXAN Optimización SEO profesional para tu negocio https://seoxan.es https://uptime.urtix.es #iPadProM5 #AppleM5 #Applelianos #FiltraciónApple #UnboxingiPad #iPadOS26 #AppleSilicon #Geekbench #Apple2025 #PodcastApple #TecnologíaApple #iPadProM4 #ComparativaApple #AppleNews #Metal #AnTuTu #RAMiPad #ReviewiPad #NuevoiPadPro #ApplePodcast #iPadProReview

professorjrod@gmail.comWhat if the real cause of your random reboots isn't the GPU at all—but the power plan behind it? We take you end to end through a stability-first build, starting with the underrated hero of every system: clean, properly sized power. You'll learn how to calculate wattage with 25–30% headroom, navigate 80 Plus efficiency tiers, and safely adopt ATX 3.0 with the 12VHPWR connector—no sharp bends, modular cable sanity, and the UPS/surge stack that prevents nasty surprises when the lights flicker.From there, we shift into storage strategy that balances speed and safety. HDD, SATA SSD, and NVMe each earn their place, and we break down RAID 0/1/5/6/10 in plain language so you can pick the right array for your workload. We underline a hard truth: RAID protects against disk failure, not human error, so versioned offsite backups remain non-negotiable. Real-world stories—including a painful RAID 5 rebuild gone wrong—highlight why RAID 6 and RAID 10 matter for bigger or busier systems.Memory and CPU round out the backbone. We simplify DDR4 vs DDR5, explain how frequency and CAS affect real latency, and show why matched pairs and dual channel deliver the performance you paid for. You'll get quick wins like enabling XMP/EXPO, when ECC is worth it, and how to troubleshoot training hiccups. Then we open the CPU: cores, threads, cache, sockets, chipsets, and why firmware comes before hardware when upgrades fail to post. Cooling decisions—air, AIO, or custom—tie directly to performance ceilings, along with safe overclock/undervolt practices and thermal targets under sustained load.By the end, you'll have a practical checklist to build smarter, troubleshoot faster, and feel ready for the CompTIA A+ exam: power headroom, cable stewardship, airflow planning, RAID with backups, memory matching, BIOS compatibility, and validation testing. If this guide helps you ship a rock-solid PC, share it with a friend, leave a quick review, and hit follow so you never miss the next masterclass.Support the showIf you want to help me with my research please e-mail me.Professorjrod@gmail.comIf you want to join my question/answer zoom class e-mail me at Professorjrod@gmail.comArt By Sarah/DesmondMusic by Joakim KarudLittle chacha ProductionsJuan Rodriguez can be reached atTikTok @ProfessorJrodProfessorJRod@gmail.com@Prof_JRodInstagram ProfessorJRod

AI networks are driving dramatic changes in data center design, especially around power, cooling, and connectivity. Modern GPU-powered AI data centers require far more energy and generate much more heat than traditional CPU-based setups, pushing cabinets to new power densities and necessitating advanced cooling solutions like liquid direct-to-chip cooling. These environments also demand significantly more fiber cabling to handle increased data flows, with deeper cabinets and complex layouts that make traditional rear-access cabling impractical.

Cerebrium is a serverless AI infrastructure platform orchestrating CPU and GPU compute for companies building voice agents, healthcare AI systems, manufacturing defect detection, and LLM hosting. The company operates across global markets handling data residency constraints from GDPR to Saudi Arabia's data sovereignty requirements. In a recent episode of Category Visionaries, I sat down with Michael Louis, Co-Founder & CEO of Cerebrium, to explore how they built a high-performance infrastructure business serving enterprise customers with high five-figure to six-figure ACVs while maintaining 99.9%+ SLA requirements. Topics Discussed: Building AI infrastructure before the GPT moment and strategic patience during the hype cycle Scaling a distributed engineering team between Cape Town and NYC with 95% South African talent Partnership-driven revenue generation producing millions in ARR without traditional sales teams AI-powered market engineering achieving 35% LinkedIn reply rates through competitor analysis Technical differentiation through cold start optimization and network latency improvements Revenue expansion through global deployment and regulatory compliance automation GTM Lessons For B2B Founders: Treat go-to-market as a systems engineering problem: Michael reframed traditional sales challenges through an engineering lens, focusing on constraints, scalability, and data-driven optimization. "I try to reframe my go to market problem as an engineering one and try to pick up, okay, like what are my constraints? Like how can I do this, how can it scale?" This systematic approach led to testing 8-10 different strategies, measuring conversion rates, and building automated pipelines rather than relying on manual processes that don't scale. Structure partnerships for partner success before revenue sharing: Cerebrium generates millions in ARR through partners whose sales teams actively upsell their product. Their approach eliminates typical partnership friction: "We typically approach our partners saying like, look, you keep the money you make, we'll keep the money we make. If it goes well, we can talk about like rev share or some other agreement down the line." This removes commission complexity that kills B2B partnerships and allows partners to focus on customer value rather than internal revenue allocation conflicts. Build AI-powered competitive intelligence for outbound at scale: Cerebrium's 35% LinkedIn reply rate comes from scraping competitor followers and LinkedIn engagement, running prospects through qualification agents that check funding status, ICP fit, and technical roles, then generating personalized outreach referencing specific interactions. "We saw you commented on Michael's post about latency in voice. Like, we think that's interesting. Like, here's a case study we did in the voice space." The system processes thousands of prospects while maintaining personalization depth that manual processes can't match. Position infrastructure as revenue expansion, not cost optimization: While dev tools typically focus on developer productivity gains, Cerebrium frames their value proposition around market expansion and revenue growth. "We allow you to deploy your application in many different markets globally... go to market leaders love us and sales leaders because again we open up more markets for them and more revenue without getting their tech team involved." This messaging resonates with revenue stakeholders and justifies higher spending compared to pure cost-reduction positioning. Weaponize regulatory complexity as competitive differentiation: Cerebrium abstracts data sovereignty requirements across multiple jurisdictions - GDPR in Europe, data residency in Saudi Arabia, and other regional compliance frameworks. "As a company to build the infrastructure to have data sovereignty in all these companies and markets, it's a nightmare." By handling this complexity, they create significant switching costs and enable customers to expand internationally without engineering roadmap dependencies, making them essential to sales teams pursuing global accounts.   //   Sponsors: Front Lines — We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. www.FrontLines.io The Global Talent Co. — We help tech startups find, vet, hire, pay, and retain amazing marketing talent that costs 50-70% less than the US & Europe.  www.GlobalTalent.co   //   Don't Miss: New Podcast Series — How I Hire Senior GTM leaders share the tactical hiring frameworks they use to build winning revenue teams. Hosted by Andy Mowat, who scaled 4 unicorns from $10M to $100M+ ARR and launched Whispered to help executives find their next role. Subscribe here: https://open.spotify.com/show/53yCHlPfLSMFimtv0riPyM   

美國政府一入股就賺50億美元! 為什麼CPU可以一直吃老本? 人做晶片你做晶片，你做到虧損是什麼玩法? Intel復興之路值得期待嗎? 現在入場是好時機?

Voices of Oxide on the pod! Cliff Biffle (engineer), Dave Pacheco (engineer), and Ben Leonard (designer) are on the show today. Jerod and I were invited to Oxide's annual internal conference called OxCon to meet the people and to hear the stories of what makes Oxide a truly special place to work right now. Cliff Biffle is working on all Hubris and firmware. Cliff says "There's a lot that happens before the 'main CPU' can even power on." Dave Pacheco is leading the efforts on Oxide's "Update" system. And Ben Leonard in charge of all things brand and design at Oxide.

Voices of Oxide on the pod! Cliff Biffle (engineer), Dave Pacheco (engineer), and Ben Leonard (designer) are on the show today. Jerod and I were invited to Oxide's annual internal conference called OxCon to meet the people and to hear the stories of what makes Oxide a truly special place to work right now. Cliff Biffle is working on all Hubris and firmware. Cliff says "There's a lot that happens before the 'main CPU' can even power on." Dave Pacheco is leading the efforts on Oxide's "Update" system. And Ben Leonard in charge of all things brand and design at Oxide.

Scriv's CPU is busted, so today's episode we bring you a conversation on how to bring characters to life! We'll talk therapy for Batman, whether there even IS a One Piece, whether we're "Pantsers" or "Plotters," and even about how the plot of Transdimensional High developed from the main characters!

Elizabeth Figura, a Wine Developer at CodeWeavers, speaks with SE Radio host Jeremy Jung about the Wine compatibility layer and the Proton distribution. They discuss a wide range of details including system calls, what people run with Wine, how games are built differently, conformance and regression testing, native performance, emulating a CPU vs emulating system calls, the role of the Proton downstream distribution, improving Wine compatibility by patching the Linux kernel and other related projects, Wine's history and sustainment, the Crossover commercial distribution, porting games without source code, loading executables and linked libraries, the difference between user space and kernel space, poor Windows API documentation and use of private APIs, debugging compatibility issues, and contributing to the project. This episode is sponsored by Monday Dev

When time-to-action requires very low latency, the immediacy of data visualization makes all the difference. Being able to analyze vast amounts of multi-dimensional data in real-time requires massive throughput, and an in-memory architecture designed to deliver instant insights at scale. Check out this episode of DM Radio to hear how advanced optimization techniques leveraging multi-core CPU, GPU, contiguous memory, and advanced compression are re-inventing what is possible. Marc Stevens and Mikhail Pikalov of Row64 will demonstrate several use cases where traditional approaches would falter. Attendees will learn: * How the real-time visualization of data changes decision-making dynamics when seconds matter; * How hardware-accelerated computing stacks can deliver speed and scale to visualization layers; * Practical use cases, from cyber security to city intelligence, where ultra-low-latency visualization drives faster, better decisions; * Key architectural principles for building environments that deliver immediacy, scalability, and reliability.

Paul Thurrott reports live from Maui with exciting details on Qualcomm's next-gen Snapdragon X2 Elite chip and how it could shake up the PC world, while behind the scenes, Microsoft quietly drifts further from OpenAI just as an NVIDIA mega-deal makes headlines. Is Windows about to get its biggest reboot in years, and can ARM finally topple Intel? Windows 25H2 is imminent: The real ISOs and eKBs are here! Paul's Arm-based trip to Mexico and Arm-based Apple-tastic experience at Snapdragon Summit And yet. It's Week D. And we didn't get any preview updates (for 24H2) Windows AI Labs is a thing If you're migrating from Windows 10 get a Windows 11 on Arm PC, Microsoft suggests New AI features coming to Notepad, Paint, and Snipping Tool New Dev and Beta (and Canary) builds: Click to Do translation, Share with Copilot, Accounts management improvements AI The Microsoft/OpenAI rift widens yet again NVIDIA invests $100 billion in OpenAI, days after "investing" $5 billion in Intel Intel will keep making its own GPUs because who gives a crap Microsoft is bringing Anthropic Claude to Microsoft 365 Copilot - "Model choice" Microsoft reportedly trying to pay publishers for content used by AI Microsoft Teams is getting more agents Google Chrome is getting a major AI update Snapdragon Summit 2025 6G, AI as the new UI, glasses as the next wave, Android PCs out of nowhere X2 Elite and X2 Elite Extreme (with up to 18 cores for ultra-premium PCs) 3rd Gen Oryon CPU (X2 was 1st gen, last year's phone chip was G2) 75 percent faster CPU perf than competition at ISO power First Arm chip to hit 5+ GHz New Adreno GPU architecture with 2.3x perf per watt and power efficiency over previous gen Hexagon NPU with 80 TOPS for "concurrent AI experiences" on Copilot+ PCs Supports latest 5G SD X75 modem, Wi-Fi 7, BT 5.4 75 percent faster CPU perf than competition at ISO power Bad news: First half of 2026 availability Not in the press release: The secret of why X2 Elite Extreme is so fast Xbox Microsoft raises Xbox console prices for the second time in 2025 Here comes the Gaming Copilot on Windows 11 Google is copying it on Android and bringing Android and native games to Windows now Tips and Picks Tip of the week: Think of 1 story for everyone you care about App pick of the week: Notion 3.0 RunAs Radio this week: Managing Vendor Incidents with Mandi Walls Brown liquor pick of the week: High Coast Whisky Quercus IV Mongolica Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: threatlocker.com/twit uscloud.com cachefly.com/twit

Paul Thurrott reports live from Maui with exciting details on Qualcomm's next-gen Snapdragon X2 Elite chip and how it could shake up the PC world, while behind the scenes, Microsoft quietly drifts further from OpenAI just as an NVIDIA mega-deal makes headlines. Is Windows about to get its biggest reboot in years, and can ARM finally topple Intel? Windows 25H2 is imminent: The real ISOs and eKBs are here! Paul's Arm-based trip to Mexico and Arm-based Apple-tastic experience at Snapdragon Summit And yet. It's Week D. And we didn't get any preview updates (for 24H2) Windows AI Labs is a thing If you're migrating from Windows 10 get a Windows 11 on Arm PC, Microsoft suggests New AI features coming to Notepad, Paint, and Snipping Tool New Dev and Beta (and Canary) builds: Click to Do translation, Share with Copilot, Accounts management improvements AI The Microsoft/OpenAI rift widens yet again NVIDIA invests $100 billion in OpenAI, days after "investing" $5 billion in Intel Intel will keep making its own GPUs because who gives a crap Microsoft is bringing Anthropic Claude to Microsoft 365 Copilot - "Model choice" Microsoft reportedly trying to pay publishers for content used by AI Microsoft Teams is getting more agents Google Chrome is getting a major AI update Snapdragon Summit 2025 6G, AI as the new UI, glasses as the next wave, Android PCs out of nowhere X2 Elite and X2 Elite Extreme (with up to 18 cores for ultra-premium PCs) 3rd Gen Oryon CPU (X2 was 1st gen, last year's phone chip was G2) 75 percent faster CPU perf than competition at ISO power First Arm chip to hit 5+ GHz New Adreno GPU architecture with 2.3x perf per watt and power efficiency over previous gen Hexagon NPU with 80 TOPS for "concurrent AI experiences" on Copilot+ PCs Supports latest 5G SD X75 modem, Wi-Fi 7, BT 5.4 75 percent faster CPU perf than competition at ISO power Bad news: First half of 2026 availability Not in the press release: The secret of why X2 Elite Extreme is so fast Xbox Microsoft raises Xbox console prices for the second time in 2025 Here comes the Gaming Copilot on Windows 11 Google is copying it on Android and bringing Android and native games to Windows now Tips and Picks Tip of the week: Think of 1 story for everyone you care about App pick of the week: Notion 3.0 RunAs Radio this week: Managing Vendor Incidents with Mandi Walls Brown liquor pick of the week: High Coast Whisky Quercus IV Mongolica Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: threatlocker.com/twit uscloud.com cachefly.com/twit

Paul Thurrott reports live from Maui with exciting details on Qualcomm's next-gen Snapdragon X2 Elite chip and how it could shake up the PC world, while behind the scenes, Microsoft quietly drifts further from OpenAI just as an NVIDIA mega-deal makes headlines. Is Windows about to get its biggest reboot in years, and can ARM finally topple Intel? Windows 25H2 is imminent: The real ISOs and eKBs are here! Paul's Arm-based trip to Mexico and Arm-based Apple-tastic experience at Snapdragon Summit And yet. It's Week D. And we didn't get any preview updates (for 24H2) Windows AI Labs is a thing If you're migrating from Windows 10 get a Windows 11 on Arm PC, Microsoft suggests New AI features coming to Notepad, Paint, and Snipping Tool New Dev and Beta (and Canary) builds: Click to Do translation, Share with Copilot, Accounts management improvements AI The Microsoft/OpenAI rift widens yet again NVIDIA invests $100 billion in OpenAI, days after "investing" $5 billion in Intel Intel will keep making its own GPUs because who gives a crap Microsoft is bringing Anthropic Claude to Microsoft 365 Copilot - "Model choice" Microsoft reportedly trying to pay publishers for content used by AI Microsoft Teams is getting more agents Google Chrome is getting a major AI update Snapdragon Summit 2025 6G, AI as the new UI, glasses as the next wave, Android PCs out of nowhere X2 Elite and X2 Elite Extreme (with up to 18 cores for ultra-premium PCs) 3rd Gen Oryon CPU (X2 was 1st gen, last year's phone chip was G2) 75 percent faster CPU perf than competition at ISO power First Arm chip to hit 5+ GHz New Adreno GPU architecture with 2.3x perf per watt and power efficiency over previous gen Hexagon NPU with 80 TOPS for "concurrent AI experiences" on Copilot+ PCs Supports latest 5G SD X75 modem, Wi-Fi 7, BT 5.4 75 percent faster CPU perf than competition at ISO power Bad news: First half of 2026 availability Not in the press release: The secret of why X2 Elite Extreme is so fast Xbox Microsoft raises Xbox console prices for the second time in 2025 Here comes the Gaming Copilot on Windows 11 Google is copying it on Android and bringing Android and native games to Windows now Tips and Picks Tip of the week: Think of 1 story for everyone you care about App pick of the week: Notion 3.0 RunAs Radio this week: Managing Vendor Incidents with Mandi Walls Brown liquor pick of the week: High Coast Whisky Quercus IV Mongolica Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: threatlocker.com/twit uscloud.com cachefly.com/twit

Paul Thurrott reports live from Maui with exciting details on Qualcomm's next-gen Snapdragon X2 Elite chip and how it could shake up the PC world, while behind the scenes, Microsoft quietly drifts further from OpenAI just as an NVIDIA mega-deal makes headlines. Is Windows about to get its biggest reboot in years, and can ARM finally topple Intel? Windows 25H2 is imminent: The real ISOs and eKBs are here! Paul's Arm-based trip to Mexico and Arm-based Apple-tastic experience at Snapdragon Summit And yet. It's Week D. And we didn't get any preview updates (for 24H2) Windows AI Labs is a thing If you're migrating from Windows 10 get a Windows 11 on Arm PC, Microsoft suggests New AI features coming to Notepad, Paint, and Snipping Tool New Dev and Beta (and Canary) builds: Click to Do translation, Share with Copilot, Accounts management improvements AI The Microsoft/OpenAI rift widens yet again NVIDIA invests $100 billion in OpenAI, days after "investing" $5 billion in Intel Intel will keep making its own GPUs because who gives a crap Microsoft is bringing Anthropic Claude to Microsoft 365 Copilot - "Model choice" Microsoft reportedly trying to pay publishers for content used by AI Microsoft Teams is getting more agents Google Chrome is getting a major AI update Snapdragon Summit 2025 6G, AI as the new UI, glasses as the next wave, Android PCs out of nowhere X2 Elite and X2 Elite Extreme (with up to 18 cores for ultra-premium PCs) 3rd Gen Oryon CPU (X2 was 1st gen, last year's phone chip was G2) 75 percent faster CPU perf than competition at ISO power First Arm chip to hit 5+ GHz New Adreno GPU architecture with 2.3x perf per watt and power efficiency over previous gen Hexagon NPU with 80 TOPS for "concurrent AI experiences" on Copilot+ PCs Supports latest 5G SD X75 modem, Wi-Fi 7, BT 5.4 75 percent faster CPU perf than competition at ISO power Bad news: First half of 2026 availability Not in the press release: The secret of why X2 Elite Extreme is so fast Xbox Microsoft raises Xbox console prices for the second time in 2025 Here comes the Gaming Copilot on Windows 11 Google is copying it on Android and bringing Android and native games to Windows now Tips and Picks Tip of the week: Think of 1 story for everyone you care about App pick of the week: Notion 3.0 RunAs Radio this week: Managing Vendor Incidents with Mandi Walls Brown liquor pick of the week: High Coast Whisky Quercus IV Mongolica Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: threatlocker.com/twit uscloud.com cachefly.com/twit

Paul Thurrott reports live from Maui with exciting details on Qualcomm's next-gen Snapdragon X2 Elite chip and how it could shake up the PC world, while behind the scenes, Microsoft quietly drifts further from OpenAI just as an NVIDIA mega-deal makes headlines. Is Windows about to get its biggest reboot in years, and can ARM finally topple Intel? Windows 25H2 is imminent: The real ISOs and eKBs are here! Paul's Arm-based trip to Mexico and Arm-based Apple-tastic experience at Snapdragon Summit And yet. It's Week D. And we didn't get any preview updates (for 24H2) Windows AI Labs is a thing If you're migrating from Windows 10 get a Windows 11 on Arm PC, Microsoft suggests New AI features coming to Notepad, Paint, and Snipping Tool New Dev and Beta (and Canary) builds: Click to Do translation, Share with Copilot, Accounts management improvements AI The Microsoft/OpenAI rift widens yet again NVIDIA invests $100 billion in OpenAI, days after "investing" $5 billion in Intel Intel will keep making its own GPUs because who gives a crap Microsoft is bringing Anthropic Claude to Microsoft 365 Copilot - "Model choice" Microsoft reportedly trying to pay publishers for content used by AI Microsoft Teams is getting more agents Google Chrome is getting a major AI update Snapdragon Summit 2025 6G, AI as the new UI, glasses as the next wave, Android PCs out of nowhere X2 Elite and X2 Elite Extreme (with up to 18 cores for ultra-premium PCs) 3rd Gen Oryon CPU (X2 was 1st gen, last year's phone chip was G2) 75 percent faster CPU perf than competition at ISO power First Arm chip to hit 5+ GHz New Adreno GPU architecture with 2.3x perf per watt and power efficiency over previous gen Hexagon NPU with 80 TOPS for "concurrent AI experiences" on Copilot+ PCs Supports latest 5G SD X75 modem, Wi-Fi 7, BT 5.4 75 percent faster CPU perf than competition at ISO power Bad news: First half of 2026 availability Not in the press release: The secret of why X2 Elite Extreme is so fast Xbox Microsoft raises Xbox console prices for the second time in 2025 Here comes the Gaming Copilot on Windows 11 Google is copying it on Android and bringing Android and native games to Windows now Tips and Picks Tip of the week: Think of 1 story for everyone you care about App pick of the week: Notion 3.0 RunAs Radio this week: Managing Vendor Incidents with Mandi Walls Brown liquor pick of the week: High Coast Whisky Quercus IV Mongolica Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: threatlocker.com/twit uscloud.com cachefly.com/twit

Elizabeth Figura is a Wine developer at Code Weavers. We discuss how Wine and Proton make it possible to run Windows applications on other operating systems. Related links WineHQ Proton Crossover Direct3D MoltenVK XAudio2 Mesa 3D Graphics Library Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Elizabeth Figuera. She's a wine developer at Code Weavers. And today we're gonna talk about what that is and, uh, all the work that goes into it. [00:00:09] Elizabeth: Thank you Jeremy. I'm glad to be here. What's Wine [00:00:13] Jeremy: I think the first thing we should talk about is maybe saying what Wine is because I think a lot of people aren't familiar with the project. [00:00:20] Elizabeth: So wine is a translation layer. in fact, I would say wine is a Windows emulator. That is what the name originally stood for. it re implements the entire windows. Or you say win 32 API. so that programs that make calls into the API, will then transfer that code to wine and and we allow that Windows programs to run on, things that are not windows. So Linux, Mac, os, other operating systems such as Solaris and BSD. it works not by emulating the CPU, but by re-implementing every API, basically from scratch and translating them to their equivalent or writing new code in case there is no, you know, equivalent. System Calls [00:01:06] Jeremy: I believe what you're doing is you're emulating system calls. Could you explain what those are and, and how that relates to the project? [00:01:15] Elizabeth: Yeah. so system call in general can be used, referred to a call into the operating system, to execute some functionality that's built into the operating system. often it's used in the context of talking to the kernel windows applications actually tend to talk at a much higher level, because there's so much, so much high level functionality built into Windows. When you think about, as opposed to other operating systems that we basically, we end up end implementing much higher level behavior than you would on Linux. [00:01:49] Jeremy: And can you give some examples of what some of those system calls would be and, I suppose how they may be higher level than some of the Linux ones. [00:01:57] Elizabeth: Sure. So of course you have like low level calls like interacting with a file system, you know, created file and read and write and such. you also have, uh, high level APIs who interact with a sound driver. [00:02:12] Elizabeth: There's, uh, one I was working on earlier today, called XAudio where you, actually, you know, build this bank of of sounds. It's meant to be, played in a game and then you can position them in various 3D space. And the, and the operating system in a sense will, take care of all of the math that goes into making that work. [00:02:36] Elizabeth: That's all running on your computer and. And then it'll send that audio data to the sound card once it's transformed it. So it sounds like it's coming from a certain space. a lot of other things like, you know, parsing XML is another big one. That there's a lot of things. The, there, the, the, the space is honestly huge [00:02:59] Jeremy: And yeah, I can sort of see how those might be things you might not expect to be done by the operating system. Like you gave the example of 3D audio and XML parsing and I think XML parsing in, in particular, you would've thought that that would be something that would be handled by the, the standard library of whatever language the person was writing their application as. [00:03:22] Jeremy: So that's interesting that it's built into the os. [00:03:25] Elizabeth: Yeah. Well, and languages like, see it's not, it isn't even part of the standard library. It's higher level than that. It's, you have specific libraries that are widespread but not. Codified in a standard, but in Windows you, in Windows, they are part of the operating system. And in fact, there's several different, XML parsers in the operating system. Microsoft likes to deprecate old APIs and make new ones that do the same thing very often. [00:03:53] Jeremy: And something I've heard about Windows is that they're typically very reluctant to break backwards compatibility. So you say they're deprecated, but do they typically keep all of them still in there? [00:04:04] Elizabeth: It all still It all still works. [00:04:07] Jeremy: And that's all things that wine has to implement as well to make sure that the software works as well. [00:04:14] Jeremy: Yeah. [00:04:14] Elizabeth: Yeah. And, and we also, you know, need to make it work. we also need to implement those things to make old, programs work because there is, uh, a lot of demand, at least from, at least from people using wine for making, for getting some really old programs, working from the. Early nineties even. What people run with Wine (Productivity, build systems, servers) [00:04:36] Jeremy: And that's probably a good, thing to talk about in terms of what, what are the types of software that, that people are trying to run with wine, and what operating system are they typically using? [00:04:46] Elizabeth: Oh, in terms of software, literally all kinds, any software you can imagine that runs on Windows, people will try to run it on wine. So we're talking games, office software productivity, software accounting. people will run, build systems on wine, build their, just run, uh, build their programs using, on visual studio, running on wine. people will run wine on servers, for example, like software as a service kind of things where you don't even know that it's running on wine. really super domain specific stuff. Like I've run astronomy, software, and wine. Design, computer assisted design, even hardware drivers can sometimes work unwind. There's a bit of a gray area. How games are different [00:05:29] Jeremy: Yeah, it's um, I think from. Maybe the general public, or at least from what I've seen, I think a lot of people's exposure to it is for playing games. is there something different about games versus all those other types of, productivity software and office software that, that makes supporting those different. [00:05:53] Elizabeth: Um, there's some things about it that are different. Games of course have gotten a lot of publicity lately because there's been a huge push, largely from valve, but also some other companies to get. A lot of huge, wide range of games working well under wine. And that's really panned out in the, in a way, I think, I think we've largely succeeded. [00:06:13] Elizabeth: We've made huge strides in the past several years. 5, 5, 10 years, I think. so when you talk about what makes games different, I think, one thing games tend to do is they have a very limited set of things they're working with and they often want to make things run fast, and so they're working very close to the me They're not, they're not gonna use an XML parser, for example. [00:06:44] Elizabeth: They're just gonna talk directly as, directly to the graphics driver as they can. Right. And, and probably going to do all their own sound design. You know, I did talk about that XAudio library, but a lot of games will just talk directly as, directly to the sound driver as Windows Let some, so this is a often a blessing, honestly, because it means there's less we have to implement to make them work. when you look at a lot of productivity applications, and especially, the other thing that makes some productivity applications harder is, Microsoft makes 'em, and They like to, make a library, for use in this one program like Microsoft Office and then say, well, you know, other programs might use this as well. Let's. Put it in the operating system and expose it and write an API for it and everything. And maybe some other programs use it. mostly it's just office, but it means that office relies on a lot of things from the operating system that we all have to reimplement. [00:07:44] Jeremy: Yeah, that's somewhat counterintuitive because when you think of games, you think of these really high performance things that that seem really complicated. But it sounds like from what you're saying, because they use the lower level primitives, they're actually easier in some ways to support. [00:08:01] Elizabeth: Yeah, certainly in some ways, they, yeah, they'll do things like re-implement the heap allocator because the built-in heap allocator isn't fast enough for them. That's another good example. What makes some applications hard to support (Some are hard, can't debug other people's apps) [00:08:16] Jeremy: You mentioned Microsoft's more modern, uh, office suites. I, I've noticed there's certain applications that, that aren't supported. Like, for example, I think the modern Adobe Creative Suite. What's the difference with software like that and does that also apply to the modern office suite, or is, or is that actually supported? [00:08:39] Elizabeth: Well, in one case you have, things like Microsoft using their own APIs that I mentioned with Adobe. That applies less, I suppose, but I think to some degree, I think to some degree the answer is that some applications are just hard and there's, and, and there's no way around it. And, and we can only spend so much time on a hard application. I. Debugging things. Debugging things can get very hard with wine. Let's, let me like explain that for a minute because, Because normally when you think about debugging an application, you say, oh, I'm gonna open up my debugger, pop it in, uh, break at this point, see what like all the variables are, or they're not what I expect. Or maybe wait for it to crash and then get a back trace and see where it crashed. And why you can't do that with wine, because you don't have the application, you don't have the symbols, you don't have your debugging symbols. You don't know anything about the code you're running unless you take the time to disassemble and decompile and read through it. And that's difficult every time. It's not only difficult, every time I've, I've looked at a program and been like, I really need to just. I'm gonna just try and figure out what the program is doing. [00:10:00] Elizabeth: It takes so much time and it is never worth it. And sometimes you have to, sometimes you have no other choice, but usually you end up, you ask to rely on seeing what calls it makes into the operating system and trying to guess which one of those is going wrong. Now, sometimes you'll get lucky and it'll crash in wine code, or sometimes it'll make a call into, a function that we don't implement yet, and we know, oh, we need to implement that function. But sometimes it does something, more obscure and we have to figure out, well, like all of these millions of calls it made, which one of them is, which one of them are we implementing incorrectly? So it's returning the wrong result or not doing something that it should. And, then you add onto that the. You know, all these sort of harder to debug things like memory errors that we could make. And it's, it can be very difficult and so sometimes some applications just suffer from those hard bugs. and sometimes it's also just a matter of not enough demand for something for us to spend a lot of time on it. [00:11:11] Elizabeth: Right. [00:11:14] Jeremy: Yeah, I can see how that would be really challenging because you're, like you were saying, you don't have the symbols, so you don't have the source code, so you don't know what any of this software you're supporting, how it was actually written. And you were saying that I. A lot of times, you know, there may be some behavior that's wrong or a crash, but it's not because wine crashed or there was an error in wine. [00:11:42] Jeremy: so you just know the system calls it made, but you don't know which of the system calls didn't behave the way that the application expected. [00:11:50] Elizabeth: Exactly. Test suite (Half the code is tests) [00:11:52] Jeremy: I can see how that would be really challenging. and wine runs so many different applications. I'm, I'm kind of curious how do you even track what's working and what's not as you, you change wine because if you support thousands or tens thousands of applications, you know, how do you know when you've got a, a regression or not? [00:12:15] Elizabeth: So, it's a great question. Um, probably over half of wine by like source code volume. I actually actually check what it is, but I think it's, i, I, I think it's probably over half is what we call is tests. And these tests serve two purposes. The one purpose is a regression test. And the other purpose is they're conformance tests that test, that test how, uh, an API behaves on windows and validates that we are behaving the same way. So we write all these tests, we run them on windows and you know, write the tests to check what the windows returns, and then we run 'em on wine and make sure that that matches. and we have just such a huge body of tests to make sure that, you know, we're not breaking anything. And that every, every, all the code that we, that we get into wine that looks like, wow, it's doing that really well. Nope, that's what Windows does. The test says so. So pretty much any code that we, any new code that we get, it has to have tests to validate, to, to demonstrate that it's doing the right thing. [00:13:31] Jeremy: And so rather than testing against a specific application, seeing if it works, you're making a call to a Windows system call, seeing how it responds, and then making the same call within wine and just making sure they match. [00:13:48] Elizabeth: Yes, exactly. And that is obviously, or that is a lot more, automatable, right? Because otherwise you have to manually, you know, there's all, these are all graphical applications. [00:14:02] Elizabeth: You'd have to manually do the things and make sure they work. Um, but if you write automateable tests, you can just run them all and the machine will complain at you if it fails it continuous integration. How compatibility problems appear to users [00:14:13] Jeremy: And because there's all these potential compatibility issues where maybe a certain call doesn't behave the way an application expects. What, what are the types of what that shows when someone's using software? I mean, I, I think you mentioned crashes, but I imagine there could be all sorts of other types of behavior. [00:14:37] Elizabeth: Yes, very much so. basically anything, anything you can imagine again is, is what will happen. You can have, crashes are the easy ones because you know when and where it crashed and you can work backwards from there. but you can also get, it can, it could hang, it could not render, right? Like maybe render a black screen. for, you know, for games you could very frequently have, graphical glitches where maybe some objects won't render right? Or the entire screen will be read. Who knows? in a very bad case, you could even bring down your system and we usually say that's not wine's fault. That's the graphics library's fault. 'cause they're not supposed to do that, uh, no matter what we do. But, you know, sometimes we have to work around that anyway. but yeah, there's, there's been some very strange and idiosyncratic bugs out there too. [00:15:33] Jeremy: Yeah. And like you mentioned that uh, there's so many different things that could have gone wrong that imagine's very difficult to find. Yeah. And when software runs through wine, I think, Performance is comparable to native [00:15:49] Jeremy: A lot of our listeners will probably be familiar with running things in a virtual machine, and they know that there's a big performance impact from doing that. [00:15:57] Jeremy: How does the performance of applications compare to running natively on the original Windows OS versus virtual machines? [00:16:08] Elizabeth: So. In theory. and I, I haven't actually done this recently, so I can't speak too much to that, but in theory, the idea is it's a lot faster. so there, there, is a bit of a joke acronym to wine. wine is not an emulator, even though I started out by saying wine is an emulator, and it was originally called a Windows emulator. but what this basically means is wine is not a CPU emulator. It doesn't, when you think about emulators in a general sense, they're often, they're often emulators for specific CPUs, often older ones like, you know, the Commodore emulator or an Amiga emulator. but in this case, you have software that's written for an x86 CPU. And it's running on an x86 CPU by giving it the same instructions that it's giving on windows. It's just that when it says, now call this Windows function, it calls us instead. So that all should perform exactly the same. The only performance difference at that point is that all should perform exactly the same as opposed to a, virtual machine where you have to interpret the instructions and maybe translate them to a different instruction set. The only performance difference is going to be, in the functions that we are implementing themselves and we try to, we try to implement them to perform. As well, or almost as well as windows. There's always going to be a bit of a theoretical gap because we have to translate from say, one API to another, but we try to make that as little as possible. And in some cases, the operating system we're running on is, is just better than Windows and the libraries we're using are better than Windows. [00:18:01] Elizabeth: And so our games will run faster, for example. sometimes we can, sometimes we can, do a better job than Windows at implementing something that's, that's under our purview. there there are some games that do actually run a little bit faster in wine than they do on Windows. [00:18:22] Jeremy: Yeah, that, that reminds me of how there's these uh, gaming handhelds out now, and some of the same ones, they have a, they either let you install Linux or install windows, or they just come with a pre-installed, and I believe what I've read is that oftentimes running the same game on both operating systems, running the same game on Linux, the battery life is better and sometimes even the performance is better with these handhelds. [00:18:53] Jeremy: So it's, it's really interesting that that can even be the case. [00:18:57] Elizabeth: Yeah, it's really a testament to the huge amount of work that's gone into that, both on the wine side and on the, side of the graphics team and the colonel team. And, and of course, you know, the years of, the years of, work that's gone into Linux, even before these gaming handhelds were, were even under consideration. Proton and Valve Software's role [00:19:21] Jeremy: And something. So for people who are familiar with the handhelds, like the steam deck, they may have heard of proton. Uh, I wonder if you can explain what proton is and how it relates to wine. [00:19:37] Elizabeth: Yeah. So, proton is basically, how do I describe this? So, proton is a sort of a fork, uh, although we try to avoid the term fork. It's a, we say it's a downstream distribution because we contribute back up to wine. so it is a, it is, it is a alternate distribution fork of wine. And it's also some code that basically glues wine into, an embedding application originally intended for steam, and developed for valve. it has also been used in, others, but it has also been used in other software. it, so where proton differs from wine besides the glue part is it has some, it has some extra hacks in it for bugs that are hard to fix and easy to hack around as some quick hacks for, making games work now that are like in the process of going upstream to wine and getting their code quality improved and going through review. [00:20:54] Elizabeth: But we want the game to work now, when we distribute it. So that'll, that'll go into proton immediately. And then once we have, once the patch makes it upstream, we replace it with the version of the patch from upstream. there's other things to make it interact nicely with steam and so on. And yeah, I think, yeah, I think that's, I got it. [00:21:19] Jeremy: Yeah. And I think for people who aren't familiar, steam is like this, um, I, I don't even know what you call it, like a gaming store and a [00:21:29] Elizabeth: store game distribution service. it's got a huge variety of games on it, and you just publish. And, and it's a great way for publishers to interact with their, you know, with a wider gaming community, uh, after it, just after paying a cut to valve of their profits, they can reach a lot of people that way. And because all these games are on team and, valve wants them to work well on, on their handheld, they contracted us to basically take their entire catalog, which is huge, enormous. And trying and just step by step. Fix every game and make them all work. [00:22:10] Jeremy: So, um, and I guess for people who aren't familiar Valve, uh, softwares the company that runs steam, and so it sounds like they've asked, uh, your company to, to help improve the compatibility of their catalog. [00:22:24] Elizabeth: Yes. valve contracted us and, and again, when you're talking about wine using lower level libraries, they've also contracted a lot of other people outside of wine. Basically, the entire stack has had a tremendous, tremendous investment by valve software to make gaming on Linux work. Well. The entire stack receives changes to improve Wine compatibility [00:22:48] Jeremy: And when you refer to the entire stack, like what are some, some of those pieces, at least at a high level. [00:22:54] Elizabeth: I, I would, let's see, let me think. There is the wine project, the. Mesa Graphics Libraries. that's a, that's another, you know, uh, open source, software project that existed, has existed for a long time. But Valve has put a lot of, uh, funding and effort into it, the Linux kernel in various different ways. [00:23:17] Elizabeth: the, the desktop, uh, environment and Window Manager for, um, are also things they've invested in. [00:23:26] Jeremy: yeah. Everything that the game needs, on any level and, and that the, and that the operating system of the handheld device needs. Wine's history [00:23:37] Jeremy: And wine's been going on for quite a while. I think it's over a decade, right? [00:23:44] Elizabeth: I believe. Oh, more than, oh, far more than a decade. I believe it started in 1990, I wanna say about 1995, mid nineties. I'm, I probably have that date wrong. I believe Wine started about the mid nineties. [00:24:00] Jeremy: Mm. [00:24:00] Elizabeth: it's going on for three decades at this rate. [00:24:03] Jeremy: Wow. Okay. [00:24:06] Jeremy: And so all this time, how has the, the project sort of sustained itself? Like who's been involved and how has it been able to keep going this long? [00:24:18] Elizabeth: Uh, I think as is the case with a lot of free software, it just, it just keeps trudging along. There's been. There's been times where there's a lot of interest in wine. There's been times where there's less, and we are fortunate to be in a time where there's a lot of interest in it. we've had the same maintainer for almost this entire, almost this entire existence. Uh, Alexander Julliard, there was one person starting who started, maintained it before him and, uh, left it maintainer ship to him after a year or two. Uh, Bob Amstat. And there has been a few, there's been a few developers who have been around for a very long time. a lot of developers who have been around for a decent amount of time, but not for the entire duration. And then a very, very large number of people who come and submit a one-off fix for their individual application that they want to make work. [00:25:19] Jeremy: How does crossover relate to the wine project? Like, it sounds like you had mentioned Valve software hired you for subcontract work, but crossover itself has been around for quite a while. So how, how has that been connected to the wine project? [00:25:37] Elizabeth: So I work for, so the, so the company I work for is Code Weavers and, crossover is our flagship software. so Code Weavers is a couple different things. We have a sort of a porting service where companies will come to us and say, can we port my application usually to Mac? And then we also have a retail service where Where we basically have our own, similar to Proton, but you know, older, but the same idea where we will add some hacks into it for very difficult to solve bugs and we have a, a nice graphical interface. And then, the other thing that we're selling with crossover is support. So if you, you know, try to run a certain application and you buy crossover, you can submit a ticket saying this doesn't work and we now have a financial incentive to fix it. You know, we'll try to, we'll try to fix your, we'll spend company resources to fix your bug, right? So that's been so, so code we v has been around since 1996 and crossover, I don't know the date, but it's crossover has been around for probably about two decades, if I'm not mistaken. [00:27:01] Jeremy: And when you mention helping companies port their software to, for example, MacOS. [00:27:07] Jeremy: Is the approach that you would port it natively to MacOS APIs or is it that you would help them get it running using wine on MacOS? [00:27:21] Elizabeth: Right. That's, so that's basically what makes us so unique among porting companies is that instead of rewriting their software, we just, we just basically stick it inside of crossover and, uh, and, and make it run. [00:27:36] Elizabeth: And the idea has always been, you know, the more we implement, the more we get correct, the, the more applications will, you know, work. And sometimes it works out that way. Sometimes not really so much. And there's always work we have to do to get any given application to work, but. Yeah, so it's, it's very unusual because we don't ask companies for any of their code. We don't need it. We just fix the windows API [00:28:07] Jeremy: And, and so in that case, the ports would be let's say someone sells a MacOS version of their software. They would bundle crossover, uh, with their software. [00:28:18] Elizabeth: Right? And usually when you do this, it doesn't look like there's crossover there. Like it just looks like this software is native, but there is soft, there is crossover under the hood. Loading executables and linked libraries [00:28:32] Jeremy: And so earlier we were talking about how you're basically intercepting the system calls that these binaries are making, whether that's the executable or the, the DLLs from Windows. Um, but I think probably a lot of our listeners are not really sure how that's done. Like they, they may have built software, but they don't know, how do I basically hijack, the system calls that this application is making. [00:29:01] Jeremy: So maybe you could talk a little bit about how that works. [00:29:04] Elizabeth: So there, so there's a couple steps to go into it. when you think about a program that's say, that's a big, a big file that's got all the machine code in it, and then it's got stuff at the beginning saying, here's how the program works and here's where in the file the processor should start running. that's, that's your EXE file. And then in your DLL files are libraries that contain shared code and you have like a similar sort of file. It says, here's the entry point. That runs this function, this, you know, this pars XML function or whatever have you. [00:29:42] Elizabeth: And here's this entry point that has the generate XML function and so on and so forth. And, and, then the operating system will basically take the EXE file and see all the bits in it. Say I want to call the pars XML function. It'll load that DLL and hook it up. So it, so the processor ends up just seeing jump directly to this pars XML function and then run that and then return and so on. [00:30:14] Elizabeth: And so what wine does, is it part of wine? That's part of wine is a library, is that, you know, the implementing that parse XML and read XML function, but part of it is the loader, which is the part of the operating system that hooks everything together. And when we load, we. Redirect to our libraries. We don't have Windows libraries. [00:30:38] Elizabeth: We like, we redirect to ours and then we run our code. And then when you jump back to the program and yeah. [00:30:48] Jeremy: So it's the, the loader that's a part of wine. That's actually, I'm not sure if running the executable is the right term. [00:30:58] Elizabeth: no, I think that's, I think that's a good term. It's, it's, it's, it starts in a loader and then we say, okay, now run the, run the machine code and it's executable and then it runs and it jumps between our libraries and back and so on. [00:31:14] Jeremy: And like you were saying before, often times when it's trying to make a system call, it ends up being handled by a function that you've written in wine. And then that in turn will call the, the Linux system calls or the MacOS system calls to try and accomplish the, the same result. [00:31:36] Elizabeth: Right, exactly. [00:31:40] Jeremy: And something that I think maybe not everyone is familiar with is there's this concept of user space versus kernel space. you explain what the difference is? [00:31:51] Elizabeth: So the way I would explain, the way I would describe a kernel is it's the part of the operating system that can do anything, right? So any program, any code that runs on your computer is talking to the processor, and the processor has to be able to do anything the computer can do. [00:32:10] Elizabeth: It has to be able to talk to the hardware, it has to set up the memory space. That, so actually a very complicated task has to be able to switch to another task. and, and, and, and basically talk to another program and. You have to have something there that can do everything, but you don't want any program to be able to do everything. Um, not since the, not since the nineties. It's about when we realized that we can't do that. so the kernel is a part that can do everything. And when you need to do something that requires those, those permissions that you can't give everyone, you have to talk to the colonel and ask it, Hey, can you do this for me please? And in a very restricted way where it's only the safe things you can do. And a degree, it's also like a library, right? It's the kernel. The kernels have always existed, and since they've always just been the core standard library of the computer that does the, that does the things like read and write files, which are very, very complicated tasks under the hood, but look very simple because all you say is write this file. And talk to the hardware and abstract away all the difference between different drivers. So the kernel is doing all of these things. So because the kernel is a part that can do everything and because when you think about the kernel, it is basically one program that is always running on your computer, but it's only one program. So when a user calls the kernel, you are switching from one program to another and you're doing a lot of complicated things as part of this. You're switching to the higher privilege level where you can do anything and you're switching the state from one program to another. And so it's a it. So this is what we mean when we talk about user space, where you're running like a normal program and kernel space where you've suddenly switched into the kernel. [00:34:19] Elizabeth: Now you're executing with increased privileges in a different. idea of the process space and increased responsibility and so on. [00:34:30] Jeremy: And, and so do most applications. When you were talking about the system calls for handling 3D audio or parsing XML. Are those considered, are those system calls considered part of user space and then those things call the kernel space on your behalf, or how, how would you describe that? [00:34:50] Elizabeth: So most, so when you look at Windows, most of most of the Windows library, the vast, vast majority of it is all user space. most of these libraries that we implement never leave user space. They never need to call into the kernel. there's the, there only the core low level stuff. Things like, we need to read a file, that's a kernel call. when you need to sleep and wait for some seconds, that's a kernel. Need to talk to a different process. Things that interact with different processes in general. not just allocate memory, but allocate a page of memory, like a, from the memory manager and then that gets sub allocated by the heap allocator. so things like that. [00:35:31] Jeremy: Yeah, so if I was writing an application and I needed to open a file, for example, does, does that mean that I would have to communicate with the kernel to, to read that file? [00:35:43] Elizabeth: Right, exactly. [00:35:46] Jeremy: And so most applications, it sounds like it's gonna be a mixture. You're gonna have a lot of things that call user space calls. And then a few, you mentioned more low level ones that are gonna require you to communicate with the kernel. [00:36:00] Elizabeth: Yeah, basically. And it's worth noting that in, in all operating systems, you're, you're almost always gonna be calling a user space library. That might just be a thin wrapper over the kernel call. It might, it's gonna do like just a little bit of work in end call the kernel. [00:36:19] Jeremy: [00:36:19] Elizabeth: In fact, in Windows, that's the only way to do it. Uh, in many other operating systems, you can actually say, you can actually tell the processor to make the kernel call. There is a special instruction that does this and just, and it'll go directly to the kernel, and there's a defined interface for this. But in Windows, that interface is not defined. It's not stable. Or backwards compatible like the rest of Windows is. So even if you wanted to use it, you couldn't. and you basically have to call into the high level libraries or low level libraries, as it were, that, that tell you that create a file. And those don't do a lot. [00:37:00] Elizabeth: They just kind of tweak their parameters a little and then pass them right down to the kernel. [00:37:07] Jeremy: And so wine, it sounds like it needs to implement both the user space calls of windows, but then also the, the kernel, calls as well. But, but wine itself does that, is that only in Linux user space or MacOS user space? [00:37:27] Elizabeth: Yes. This is a very tricky thing. but all of wine, basically all of what is wine runs in, in user space and we use. Kernel calls that are already there to talk to the colonel, to talk to the host Colonel. You have to, and you, you get, you get, you get the sort of second nature of thinking about the Windows, user space and kernel. [00:37:50] Elizabeth: And then there's a host user space and Kernel and wine is running all in user, in the user, in the host user space, but it's emulating the Windows kernel. In fact, one of the weirdest, trickiest parts is I mentioned that you can run some drivers in wine. And those drivers actually, they actually are, they think they're running in the Windows kernel. which in a sense works the same way. It has libraries that it can load, and those drivers are basically libraries and they're making, kernel calls and they're, they're making calls into the kernel library that does some very, very low level tasks that. You're normally only supposed to be able to do in a kernel. And, you know, because the kernel requires some privileges, we kind of pretend we have them. And in many cases, you're even the drivers are using abstractions. We can just implement those abstractions kind of over the slightly higher level abstractions that exist in user space. [00:39:00] Jeremy: Yeah, I hadn't even considered the being able to use hardware devices, but I, I suppose if in, in the end, if you're reproducing the kernel, then whether you're running software or you're talking to a hardware device, as long as you implement the calls correctly, then I, I suppose it works. [00:39:18] Elizabeth: Cause you're, you're talking about device, like maybe it's some kind of USB device that has drivers for Windows, but it doesn't for, for Linux. [00:39:28] Elizabeth: no, that's exactly, that's a, that's kind of the, the example I've used. Uh, I think there is, I think I. My, one of my best success stories was, uh, drivers for a graphing calculator. [00:39:41] Jeremy: Oh, wow. [00:39:42] Elizabeth: That connected via USB and I basically just plugged the windows drivers into wine and, and ran it. And I had to implement a lot of things, but it worked. But for example, something like a graphics driver is not something you could implement in wine because you need the graphics driver on the host. We can't talk to the graphics driver while the host is already doing so. [00:40:05] Jeremy: I see. Yeah. And in that case it probably doesn't make sense to do so [00:40:11] Elizabeth: Right? [00:40:12] Elizabeth: Right. It doesn't because, the transition from user into kernel is complicated. You need the graphics driver to be in the kernel and the real kernel. Having it in wine would be a bad idea. Yeah. [00:40:25] Jeremy: I, I think there's, there's enough APIs you have to try and reproduce that. I, I think, uh, doing, doing something where, [00:40:32] Elizabeth: very difficult [00:40:33] Jeremy: right. Poor system call documentation and private APIs [00:40:35] Jeremy: There's so many different, calls both in user space and in kernel space. I imagine the, the user space ones Microsoft must document to some extent, but, oh. Is that, is that a [00:40:51] Elizabeth: well, sometimes, [00:40:54] Jeremy: Sometimes. Okay. [00:40:55] Elizabeth: I think it's actually better now than it used to be. But some, here's where things get fun, because sometimes there will be, you know, regular documented calls. Sometimes those calls are documented, but the documentation isn't very good. Sometimes programs will just sort of look inside Microsoft's DLLs and use calls that they aren't supposed to be using. Sometimes they use calls that they are supposed to be using, but the documentation has disappeared. just because it's that old of an API and Microsoft hasn't kept it around. sometimes some, sometimes Microsoft, Microsoft own software uses, APIs that were never documented because they never wanted anyone else using them, but they still ship them with the operating system. there was actually a kind of a lawsuit about this because it is an antitrust lawsuit, because by shipping things that only they could use, they were kind of creating a trust. and that got some things documented. At least in theory, they kind of haven't stopped doing it, though. [00:42:08] Jeremy: Oh, so even today they're, they're, I guess they would call those private, private APIs, I suppose. [00:42:14] Elizabeth: I suppose. Uh, yeah, you could say private APIs. but if we want to get, you know, newer versions of Microsoft Office running, we still have to figure out what they're doing and implement them. [00:42:25] Jeremy: And given that they're either, like you were saying, the documentation is kind of all over the place. If you don't know how it's supposed to behave, how do you even approach implementing them? [00:42:38] Elizabeth: and that's what the conformance tests are for. And I, yeah, I mentioned earlier we have this huge body of conformance tests that double is regression tests. if we see an API, we don't know what to do with or an API, we do know, we, we think we know what to do with because the documentation can just be wrong and often has been. Then we write tests to figure out what it's supposed to behave. We kind of guess until we, and, and we write tests and we pass some things in and see what comes out and see what. The see what the operating system does until we figure out, oh, so this is what it's supposed to do and these are the exact parameters in, and, and then we, and, and then we implement it according to those tests. [00:43:24] Jeremy: Is there any distinction in approach for when you're trying to implement something that's at the user level versus the kernel level? [00:43:33] Elizabeth: No, not really. And like I, and like I mentioned earlier, like, well, I mean, a kernel call is just like a library call. It's just done in a slightly different way, but it's still got, you know, parameters in, it's still got a set of parameters. They're just encoded differently. And, and again, like the, the way kernel calls are done is on a level just above the kernel where you have a library, that just passes things through. Almost verbatim to the kernel and we implement that library instead. [00:44:10] Jeremy: And, and you've been working on i, I think, wine for over, over six years now. [00:44:18] Elizabeth: That sounds about right. Debugging and having broad knowledge of Wine [00:44:20] Jeremy: What does, uh, your, your day to day look like? What parts of the project do you, do you work on? [00:44:27] Elizabeth: It really varies from day to day. and I, I, a lot of people, a lot of, some people will work on the same parts of wine for years. Uh, some people will switch around and work on all sorts of different things. [00:44:42] Elizabeth: And I'm, I definitely belong to that second group. Like if you name an area of wine, I have almost certainly contributed a patch or two to it. there's some areas I work on more than others, like, 3D graphics, multimedia, a, I had, I worked on a compiler that exists, uh, socket. So networking communication is another thing I work a lot on. day to day, I kind of just get, I, I I kind of just get a bug for some program or another. and I take it and I debug it and figure out why the program's broken and then I fix it. And there's so much variety in that. because a bug can take so many different forms like I described, and, and, and the, and then the fix can be simple or complicated or, and it can be in really anywhere to a degree. [00:45:40] Elizabeth: being able to work on any part of wine is sometimes almost a necessity because if a program is just broken, you don't know why. It could be anything. It could be any sort of API. And sometimes you can hand the API to somebody who's got a lot of experience in that, but sometimes you just do whatever. You just fix whatever's broken and you get an experience that way. [00:46:06] Jeremy: Yeah, I mean, I was gonna ask about the specialized skills to, to work on wine, but it sounds like maybe in your case it's all of them. [00:46:15] Elizabeth: It's, there's a bit of that. it's a wine. We, the skills to work on wine are very, it's a very unique set of skills because, and it largely comes down to debugging because you can't use the tools you normally use debug. [00:46:30] Elizabeth: You have to, you have to be creative and think about it different ways. Sometimes you have to be very creative. and programs will try their hardest to avoid being debugged because they don't want anyone breaking their copy protection, for example, or or hacking, or, you know, hacking in sheets. They want to be, they want, they don't want anyone hacking them like that. [00:46:54] Elizabeth: And we have to do it anyway for good and legitimate purposes. We would argue to make them work better on more operating systems. And so we have to fight that every step of the way. [00:47:07] Jeremy: Yeah, it seems like it's a combination of. F being able, like you, you were saying, being able to, to debug. and you're debugging not necessarily your own code, but you're debugging this like behavior of, [00:47:25] Jeremy: And then based on that behavior, you have to figure out, okay, where in all these different systems within wine could this part be not working? [00:47:35] Jeremy: And I, I suppose you probably build up some kind of, mental map in your head of when you get a, a type of bug or a type of crash, you oh, maybe it's this, maybe it's here, or something [00:47:47] Elizabeth: Yeah. That, yeah, there is a lot of that. there's, you notice some patterns, you know, after experience helps, but because any bug could be new, sometimes experience doesn't help and you just, you just kind of have to start from scratch. Finding a bug related to XAudio [00:48:08] Jeremy: At sort of a high level, can you give an example of where you got a specific bug report and then where you had to look to eventually find which parts of the the system were the issue? [00:48:21] Elizabeth: one, one I think good example, that I've done recently. so I mentioned this, this XAudio library that does 3D audio. And if you say you come across a bug, I'm gonna be a little bit generics here and say you come across a bug where some audio isn't playing right, maybe there's, silence where there should be the audio. So you kind of, you look in and see, well, where's that getting lost? So you can basically look in the input calls and say, here's the buffer it's submitting that's got all the audio data in it. And you look at the output, you look at where you think the output should be, like, that library will internally call a different library, which programs can interact with directly. [00:49:03] Elizabeth: And this our high level library interacts with that is the, give this sound to the audio driver, right? So you've got XAudio on top of, um. mdev, API, which is the other library that gives audio to the driver. And you see, well, the ba the buffer is that XAudio is passing into MM Dev, dev API. They're empty, there's nothing in them. So you have to kind of work through the XAudio library to see where is, where's that sound getting lost? Or maybe, or maybe that's not getting lost. Maybe it's coming through all garbled. And I've had to look at the buffer and see why is it garbled. I'll open up it up in Audacity and look at the weight shape of the wave and say, huh, that shape of the wave looks like it's, it looks like we're putting silence every 10 nanoseconds or something, or, or reversing something or interpreting it wrong. things like that. Um, there's a lot of, you'll do a lot of, putting in print fs basically all throughout wine to see where does the state change. Where was, where is it? Where is it? Right? And then where do things start going wrong? [00:50:14] Jeremy: Yeah. And in the audio example, because they're making a call to your XAudio implementation, you can see that Okay, the, the buffer, the audio that's coming in. That part is good. It, it's just that later on when it sends it to what's gonna actually have it be played by the, the hardware, that's when missing. So, [00:50:37] Elizabeth: We did something wrong in a library that destroyed the buffer. And I think on a very, high level a lot of debugging, wine is about finding where things are good and finding where things are bad, and then narrowing that down until we find the one spot where things go wrong. There's a lot of processes that go like that. [00:50:57] Jeremy: like you were saying, the more you see these problems, hopefully the, the easier it gets to, to narrow down where, [00:51:04] Elizabeth: Often. Yeah. Especially if you keep debugging things in the same area. How much code is OS specific?c [00:51:09] Jeremy: And wine supports more than one operating system. I, I saw there was Linux, MacOS I think free BSD. How much of the code is operating system specific versus how much can just be shared across all of them? [00:51:27] Elizabeth: Not that much is operating system specific actually. so when you think about the volume of wine, the, the, the, vast majority of it is the high level code that doesn't need to interact with the operating system on a low level. Right? Because Windows keeps putting, because Microsoft keeps putting lots and lots of different libraries in their operating system. And a lot of these are high level libraries. and even when we do interact with the operating system, we're, we're using cross-platform libraries or we're using, we're using ics. The, uh, so all these operating systems that we are implementing are con, basically conformed to the posix standard. which is basically like Unix, they're all Unix based. Psic is a Unix based standard. Microsoft is, you know, the big exception that never did implement that. And, and so we have to translate its APIs to Unix, APIs. now that said, there is a lot of very operating system, specific code. Apple makes things difficult by try, by diverging almost wherever they can. And so we have a lot of Apple specific code in there. [00:52:46] Jeremy: another example I can think of is, I believe MacOS doesn't support, Vulkan [00:52:53] Elizabeth: yes. Yeah.Yeah, That's a, yeah, that's a great example of Mac not wanting to use, uh, generic libraries that work on every other operating system. and in some cases we, we look at it and are like, alright, we'll implement a wrapper for that too, on top of Yuri, on top of your, uh, operating system. We've done it for Windows, we can do it for Vulkan. and that's, and then you get the Molten VK project. Uh, and to be clear, we didn't invent molten vk. It was around before us. We have contributed a lot to it. Direct3d, Vulkan, and MoltenVK [00:53:28] Jeremy: Yeah, I think maybe just at a high level might be good to explain the relationship between Direct 3D or Direct X and Vulcan and um, yeah. Yeah. Maybe if you could go into that. [00:53:42] Elizabeth: so Direct 3D is Microsoft's 3D API. the 3D APIs, you know, are, are basically a way to, they're way to firstly abstract out the differences between different graphics, graphics cards, which, you know, look very different on a hardware level. [00:54:03] Elizabeth: Especially. They, they used to look very different and they still do look very different. and secondly, a way to deal with them at a high level because actually talking to the graphics card on a low level is very, very complicated. Even talking to it on a high level is complicated, but it gets, it can get a lot worse if you've ever been a, if you've ever done any graphics, driver development. so you have a, a number of different APIs that achieve these two goals of, of, abstraction and, and of, of, of building a common abstraction and of building a, a high level abstraction. so OpenGL is the broadly the free, the free operating system world, the non Microsoft's world's choice, back in the day. [00:54:53] Elizabeth: And then direct 3D was Microsoft's API and they've and Direct 3D. And both of these have evolved over time and come up with new versions and such. And when any, API exists for too long. It gains a lot of croft and needs to be replaced. And eventually, eventually the people who developed OpenGL decided we need to start over, get rid of the Croft to make it cleaner and make it lower level. [00:55:28] Elizabeth: Because to get in a maximum performance games really want low level access. And so they made Vulcan, Microsoft kind of did the same thing, but they still call it Direct 3D. they just, it's, it's their, the newest version of Direct 3D is lower level. It's called Direct 3D 12. and, and, Mac looked at this and they decided we're gonna do the same thing too, but we're not gonna use Vulcan. [00:55:52] Elizabeth: We're gonna define our own. And they call it metal. And so when we want to translate D 3D 12 into something that another operating system understands. That's probably Vulcan. And, and on Mac, we need to translate it to metal somehow. And we decided instead of having a separate layer from D three 12 to metal, we're just gonna translate it to Vulcan and then translate the Vulcan to metal. And it also lets things written for Vulcan on Windows, which is also a thing that exists that lets them work on metal. [00:56:30] Jeremy: And having to do that translation, does that have a performance impact or is that not really felt? [00:56:38] Elizabeth: yes. It's kind of like, it's kind of like anything, when you talk about performance, like I mentioned this earlier, there's always gonna be overhead from translating from one API to another. But we try to, what we, we put in heroic efforts to. And try, try to make sure that doesn't matter, to, to make sure that stuff that needs to be fast is really as fast as it can possibly be. [00:57:06] Elizabeth: And some very clever things have been done along those lines. and, sometimes the, you know, the graphics drivers underneath are so good that it actually does run better, even despite the translation overhead. And then sometimes to make it run fast, we need to say, well, we're gonna implement a new API that behaves more like windows, so we can do less work translating it. And that's, and sometimes that goes into the graphics library and sometimes that goes into other places. Targeting Wine instead of porting applications [00:57:43] Jeremy: Yeah. Something I've found a little bit interesting about the last few years is [00:57:49] Jeremy: Developers in the past, they would generally target Windows and you might be lucky to get a Mac port or a Linux port. And I wonder, like, in your opinion now, now that a lot of developers are just targeting Windows and relying on wine or, or proton to, to run their software, is there any, I suppose, downside to doing that? [00:58:17] Jeremy: Or is it all just upside, like everyone should target Windows as this common platform? [00:58:23] Elizabeth: Yeah. It's an interesting question. I, there's some people who seem to think it's a bad thing that, that we're not getting native ports in the same sense, and then there's some people who. Who See, no, that's a perfectly valid way to do ports just right for this defacto common API it was never intended as a cross platform common API, but we've made it one. [00:58:47] Elizabeth: Right? And so why is that any worse than if it runs on a different API on on Linux or Mac and I? Yeah, I, I, I guess I tend to, I, that that argument tends to make sense to me. I don't, I don't really see, I don't personally see a lot of reason for, to, to, to say that one library is more pure than another. [00:59:12] Elizabeth: Right now, I do think Windows APIs are generally pretty bad. I, I'm, this might be, you know, just some sort of, this might just be an effect of having to work with them for a very long time and see all their flaws and have to deal with the nonsense that they do. But I think that a lot of the. Native Linux APIs are better. But if you like your Windows API better. And if you want to target Windows and that's the only way to do it, then sure why not? What's wrong with that? [00:59:51] Jeremy: Yeah, and I think the, doing it this way, targeting Windows, I mean if you look in the past, even though you had some software that would be ported to other operating systems without this compatibility layer, without people just targeting Windows, all this software that people can now run on these portable gaming handhelds or on Linux, Most of that software was never gonna be ported. So yeah, absolutely. And [01:00:21] Elizabeth: that's [01:00:22] Jeremy: having that as an option. Yeah. [01:00:24] Elizabeth: That's kind of why wine existed, because people wanted to run their software. You know, that was never gonna be ported. They just wanted, and then the community just spent a lot of effort in, you know, making all these individual programs run. Yeah. [01:00:39] Jeremy: I think it's pretty, pretty amazing too that, that now that's become this official way, I suppose, of distributing your software where you say like, Hey, I made a Windows version, but you're on your Linux machine. it's officially supported because, we have this much belief in this compatibility layer. [01:01:02] Elizabeth: it's kind of incredible to see wine having got this far. I mean, I started working on a, you know, six, seven years ago, and even then, I could never have imagined it would be like this. [01:01:16] Elizabeth: So as we, we wrap up, for the developers that are listening or, or people who are just users of wine, um, is there anything you think they should know about the project that we haven't talked about? [01:01:31] Elizabeth: I don't think there's anything I can think of. [01:01:34] Jeremy: And if people wanna learn, uh, more about the wine project or, or see what you're up to, where, where should they, where should they head? Getting support and contributing [01:01:45] Elizabeth: We don't really have any things like news, unfortunately. Um, read the release notes, uh, follow some, there's some, there's some people who, from Code Weavers who do blogs. So if you, so if you go to codeweavers.com/blog, there's some, there's, there's some codeweavers stuff, uh, some marketing stuff. But there's also some developers who will talk about bugs that they are solving and. And how it's easy and, and the experience of working on wine. [01:02:18] Jeremy: And I suppose if, if someone's. Interested in like, like let's say they have a piece of software, it's not working through wine. what's the best place for them to, to either get help or maybe even get involved with, with trying to fix it? [01:02:37] Elizabeth: yeah. Uh, so you can file a bug on, winehq.org,or, or, you know, find, there's a lot of developer resources there and you can get involved with contributing to the software. And, uh, there, there's links to our mailing list and IRC channels and, uh, and, and the GitLab, where all places you can find developers. [01:03:02] Elizabeth: We love to help you. Debug things. We love to help you fix things. We try our very best to be a welcoming community and we have got a long, we've got a lot of experience working with people who want to get their application working. So, we would love to, we'd love to have another. [01:03:24] Jeremy: Very cool. Yeah, I think wine is a really interesting project because I think for, I guess it would've been for decades, it seemed like very niche, like not many people [01:03:37] Jeremy: were aware of it. And now I think maybe in particular because of the, the Linux gaming handhelds, like the steam deck,wine is now something that a bunch of people who would've never heard about it before, and now they're aware of it. [01:03:53] Elizabeth: Absolutely. I've watched that transformation happen in real time and it's been surreal. [01:04:00] Jeremy: Very cool. Well, Elizabeth, thank you so much for, for joining me today. [01:04:05] Elizabeth: Thank you, Jeremy. I've been glad to be here.

Paul Thurrott reports live from Maui with exciting details on Qualcomm's next-gen Snapdragon X2 Elite chip and how it could shake up the PC world, while behind the scenes, Microsoft quietly drifts further from OpenAI just as an NVIDIA mega-deal makes headlines. Is Windows about to get its biggest reboot in years, and can ARM finally topple Intel? Windows 25H2 is imminent: The real ISOs and eKBs are here! Paul's Arm-based trip to Mexico and Arm-based Apple-tastic experience at Snapdragon Summit And yet. It's Week D. And we didn't get any preview updates (for 24H2) Windows AI Labs is a thing If you're migrating from Windows 10 get a Windows 11 on Arm PC, Microsoft suggests New AI features coming to Notepad, Paint, and Snipping Tool New Dev and Beta (and Canary) builds: Click to Do translation, Share with Copilot, Accounts management improvements AI The Microsoft/OpenAI rift widens yet again NVIDIA invests $100 billion in OpenAI, days after "investing" $5 billion in Intel Intel will keep making its own GPUs because who gives a crap Microsoft is bringing Anthropic Claude to Microsoft 365 Copilot - "Model choice" Microsoft reportedly trying to pay publishers for content used by AI Microsoft Teams is getting more agents Google Chrome is getting a major AI update Snapdragon Summit 2025 6G, AI as the new UI, glasses as the next wave, Android PCs out of nowhere X2 Elite and X2 Elite Extreme (with up to 18 cores for ultra-premium PCs) 3rd Gen Oryon CPU (X2 was 1st gen, last year's phone chip was G2) 75 percent faster CPU perf than competition at ISO power First Arm chip to hit 5+ GHz New Adreno GPU architecture with 2.3x perf per watt and power efficiency over previous gen Hexagon NPU with 80 TOPS for "concurrent AI experiences" on Copilot+ PCs Supports latest 5G SD X75 modem, Wi-Fi 7, BT 5.4 75 percent faster CPU perf than competition at ISO power Bad news: First half of 2026 availability Not in the press release: The secret of why X2 Elite Extreme is so fast Xbox Microsoft raises Xbox console prices for the second time in 2025 Here comes the Gaming Copilot on Windows 11 Google is copying it on Android and bringing Android and native games to Windows now Tips and Picks Tip of the week: Think of 1 story for everyone you care about App pick of the week: Notion 3.0 RunAs Radio this week: Managing Vendor Incidents with Mandi Walls Brown liquor pick of the week: High Coast Whisky Quercus IV Mongolica Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: threatlocker.com/twit uscloud.com cachefly.com/twit

Can't get enough Linux? How about multiple kernels running simultaneously, side by side, not in a VM, all on the same hardware; this week it's finally looking real.Sponsored By:Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love. 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility. Support LINUX UnpluggedLinks:

NVIDIA has made a significant move by investing $5 billion in Intel, acquiring approximately 4% ownership of the company. This partnership aims to co-develop custom data center and personal computer products, integrating NVIDIA's advanced AI and accelerated computing capabilities with Intel's leading CPU technologies. The collaboration is expected to create custom x86 chips that will be manufactured by Intel to NVIDIA's specifications, potentially generating an annual opportunity worth between $25 and $50 billion once the products are launched. Despite this partnership, Intel will continue to develop its own ARC graphic processing units, although the messaging around this dual focus may create confusion.The Federal Reserve has cut interest rates by a quarter point, a decision framed as a risk management measure amid a cooling labor market. While job gains have slowed and inflation remains high, the Fed's cautious approach indicates limited support for deeper cuts. In the tech sector, the U.S. personal computer industry is facing challenges, with shipments declining due to inventory issues and consumer reluctance to upgrade their devices, even with the impending end of support for Windows 10. This stagnation in consumer sales reflects broader economic uncertainties as buyers prioritize essential expenses.Meanwhile, global spending on artificial intelligence is projected to reach nearly $1.5 trillion this year, driven by a boom in cloud data center construction and rising enterprise investments in AI technologies. Despite the enthusiasm surrounding AI, a recent McKinsey report reveals that 80% of companies utilizing generative AI have not seen tangible impacts on their earnings, highlighting a disconnect between the hype and real-world performance. As stock prices rise, recession signals are emerging, suggesting a need for caution in an increasingly concentrated market.Managed service providers (MSPs) are strategically positioned within a $608 billion industry, despite a decline in optimism regarding significant revenue growth. The demand for managed IT services continues to rise, with many providers diversifying their revenue streams by offering consulting and design services. Additionally, IT outages are costing businesses an estimated $76 million annually, emphasizing the importance of uptime over tools. As the landscape evolves, providers must focus on delivering outcomes rather than competing solely on software, ensuring that customers receive the value they need to maintain business continuity. Three things to know today00:00 Fed Rate Cut, PC Sales Slump, and $1.5T AI Hype: Why IT Providers Must Focus on Security and Outcomes04:36 $76M Downtime Losses, Cooling MSP Optimism, 7x Security Multipliers, and Mainframe ROI—All Point to Services as the Real Value08:16 Nvidia Buys 4% of Intel in $5B Deal, Betting on Custom AI Chips for Servers and PCs This is the Business of Tech.    Supported by:  https://scalepad.com/dave/Webinar:   https://bit.ly/msprmail All our Sponsors: https://businessof.tech/sponsors/ Do you want the show on your podcast app or the written versions of the stories? Subscribe to the Business of Tech: https://www.businessof.tech/subscribe/Looking for a link from the stories? The entire script of the show, with links to articles, are posted in each story on https://www.businessof.tech/ Support the show on Patreon: https://patreon.com/mspradio/ Want to be a guest on Business of Tech: Daily 10-Minute IT Services Insights? Send Dave Sobel a message on PodMatch, here: https://www.podmatch.com/hostdetailpreview/businessoftech Want our stuff? Cool Merch? Wear “Why Do We Care?” - Visit https://mspradio.myspreadshop.com Follow us on:LinkedIn: https://www.linkedin.com/company/28908079/YouTube: https://youtube.com/mspradio/Facebook: https://www.facebook.com/mspradionews/Instagram: https://www.instagram.com/mspradio/TikTok: https://www.tiktok.com/@businessoftechBluesky: https://bsky.app/profile/businessof.tech Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Big thanks to Proton VPN for sponsoring this video. To get 64% discount to your Proton VPN Plus subscription, please use the following link: https://protonvpn.com/davidbombal Want a “hacker” laptop without wasting cash? In this candid breakdown with OTW, we cut through the hype and show you what actually matters for learning pentesting in 2025: prioritising RAM over flashy GPUs, picking VMware (free for personal use) for reliable labs, using refurbs/minis/Raspberry Pi, and planning for where wireless hacking is going (Bluetooth/BLE/Zigbee) — not just Wi-Fi. We also cover AMD vs Intel vs Apple M-chips/ARM for Linux VMs, when cloud cracking makes sense, and why daily practice beats buying gadgets. Highlights: • Best beginner specs (RAM first, SSD nice, storage ≠ speed) • VMware vs VirtualBox for home labs • AMD/Intel vs Apple M-chips/ARM for Kali/Parrot VMs • Alpha adapters & aircrack-ng compatibility; Nordic nRF52 for BLE • Budget path: used/refurb, mini-PCs, Pi, phone/cloud labs (HTB/THM) • The 80/20 rule of hacking: skills are greater than gear If you're delaying until you can afford a $2 – 3k laptop, don't. Start now, learn daily, and upgrade later. // Occupy The Web SOCIAL // X: / three_cube Website: https://hackers-arise.net/ // Occupy The Web Books // Linux Basics for Hackers 2nd Ed US: https://amzn.to/3TscpxY UK: https://amzn.to/45XaF7j Linux Basics for Hackers: US: https://amzn.to/3wqukgC UK: https://amzn.to/43PHFev Getting Started Becoming a Master Hacker US: https://amzn.to/4bmGqX2 UK: https://amzn.to/43JG2iA Network Basics for hackers: US: https://amzn.to/3yeYVyb UK: https://amzn.to/4aInbGK // OTW Discount // Use the code BOMBAL to get a 20% discount off anything from OTW's website: https://hackers-arise.net/ // Playlists REFERENCE // Linux Basics for Hackers: • Linux for Hackers Tutorial (And Free Courses) Mr Robot: • Hack like Mr Robot // WiFi, Bluetooth and ... Hackers Arise / Occupy the Web Hacks: • Hacking Tools (with demos) that you need t... // David's SOCIAL // Discord: discord.com/invite/usKSyzb Twitter: www.twitter.com/davidbombal Instagram: www.instagram.com/davidbombal LinkedIn: www.linkedin.com/in/davidbombal Facebook: www.facebook.com/davidbombal.co TikTok: tiktok.com/@davidbombal YouTube: / @davidbombal Spotify: open.spotify.com/show/3f6k6gE... SoundCloud: / davidbombal Apple Podcast: podcasts.apple.com/us/podcast... // MY STUFF // https://www.amazon.com/shop/davidbombal // SPONSORS // Interested in sponsoring my videos? Reach out to my team here: sponsors@davidbombal.com // MENU // 0:00 - Coming up 01:21 - Proton VPN sponsored segment 03:16 - Get started and start learning 08:39 - Computer specs: CPU, GPU, RAM & Hard drives 16:46 - Time vs Money 17:58 - Virtual machines 19:15 - Computer specs overview 22:17 - Wi-Fi adaptors for Wi-Fi hacking 24:17 - Bluetooth dongles for Bluetooth hacking 26:57 - "80% Person & 20% Machine" 29:17 - Do you need hacking gadgets? 31:57 - Apple vs Intel vs AMD 35:53 - Learn hacking with a smartphone 37:01 - Learn hacking with a Raspberry Pi 39:32 - Kali Linux vs ParrotOS (Which OS to use?) 40:58 - The problem with Chromebooks 42:02 - Using Hack The Box/TryHackMe // Conclusion Please note that links listed may be affiliate links and provide me with a small percentage/kickback should you use them to purchase any of the items listed or recommended. Thank you for supporting me and this channel! Disclaimer: This video is for educational purposes only. #hacking #laptop #vm

We've been tinkering with a lot of esoteric PC hardware stuff lately, so we're here with a roundup on what we've been up to this week that you'll hopefully find informative. We get into Microsoft's crackdown on the vulnerability in FanControl and other popular monitoring software, attempting to corral fan settings in UEFI as an alternative, and doing battle with the dreaded beat frequencies that can result from adjacent fan placement. Brad also gives a full trip report on his attempt to power a stack of hard drives with an external ATX power supply, with a detour into handy tips for de-pinning a modular power supply cable, stacking multiple hard drives, and more. And Will touches on his recent experience building a new studio PC in a rack-mounted case, plus some tidbits about the last electronics flea market of the year, Linux thread scheduling, Brad's first trip to Micro Center, Will's shiny new CRT (yes, another one), and more!Links for this episode:WinRing0: Why Windows is flagging your PC monitoring and fan control apps as a threat: https://www.theverge.com/report/629259/winring0-windows-defender-fan-control-pc-monitoring-alert-quarantineNoctua on fan placement and beat frequencies: https://noctua.at/en/fan-speed-offset-explainedStackable hard drive feet Brad bought: https://sednashop.com/index.php?route=product/product&product_id=95Seasonic pinout and cable compatibility info: https://seasonic.com/cable-compatibility/How to de-pin a power supply cable with two staples: https://www.youtube.com/watch?v=n6gQ5ie2Dw0Brad's NAS/hard drive setup and de-pinned cable: https://imgur.com/a/WKPwhCQ Support the Pod! Contribute to the Tech Pod Patreon and get access to our booming Discord, a monthly bonus episode, your name in the credits, and other great benefits! You can support the show at: https://patreon.com/techpod

欢迎收听雪球出品的财经有深度，雪球，国内领先的集投资交流交易一体的综合财富管理平台，聪明的投资者都在这里。今天分享的内容叫关于英伟达入股英特尔的几点看法。来自雨枫。2025年9月18日，全球GPU巨头英伟达宣布，将以50亿美元的巨额投资入股其传统竞争对手英特尔，同时双方将在人工智能基础设施和个人计算机产品领域展开深度合作。我就此发表我的几点看法。第一，单纯就是跟英伟达结成深度的战略合作关系，即使先不考虑那50亿美元，对于这两年深陷泥潭的英特尔以数据为中心的人工智能来说，也是一剂强心针。毕竟各条业务线当中，受到压力最大、丢失份额最多的就是这块了。反而对面向消费级的全球化智库来说，继续用自己的核显还是集成英伟达的显卡，销量上的区别其实并不会有那么大。第二，对于英特尔来说，如今所面临的问题，短期来看是制程研发、是服务器CPU份额流失、是要不要转型无晶圆厂模式公司。但长期来看，一切苦难的根源，还是因为x86市场本身在不断萎缩，日渐衰弱的主营业务收入，覆盖不了下一代制程研发和生产所需的巨额资本开销，这才是今天所有问题的根源。第三，长期来看，美国政府会想尽一切办法让本土的无晶圆厂转移一部分订单给英特尔，包括但不限于关税层面和更强硬的司法层面。所以现在没有公布制程方面的代工合作，不代表后面不可以有。不过另一方面，这也说明18A这代制程，眼下确实还打动不了英伟达；第四，陈立武既然上台伊始没有选择分拆IFS公司，还拿了特朗普政府的钱，那起码在短时间内，就更不可能选择分拆了。所以换个角度来说，要想让英特尔彻底活过来，最重要的三件事：订单、订单、还是订单。其他都不是问题的关键。这个原则，也适用于和英伟达的合作。第五，9月18日晚有一个很大的疑问是英特尔自研的显卡业务线还要不要继续保留，还是说以后彻底就放弃了这方面的所有念想？如果是后者的话，那这50亿美元对英特尔来说还是挺昂贵的。第六，黄仁勋这个操作，在一定程度上也是对AMD的一种反制，毕竟AMD这两年能活得这么滋润，甚至还有余力去挑战老黄在AI市场上的江湖地位，说到底还是因为在x86服务器业务上赚到了真金白银。如果老黄能通过与英特尔的合作，在服务器芯片市场上给AMD施加更大的压力，那其实也是一种变相的围魏救赵之举。退一万步说，如果是单纯为了高速显卡互连技术和GPU方面的合作，英伟达其实犯不上非要花钱入股。毕竟以英伟达目前的市场地位，老黄只要招招手，陈立武就得跑过去候着。选择入股，本身就说明了一些事情。第七，对于英伟达来说，丧失增长性的x86市场肯定不是它所感兴趣的蛋糕，但却是它无论如何也绕不开的一道墙。想用ARM彻底取代x86，听起来确实是很美好的，但具体实施的过程却存在着无数的障碍，何况如今的ARM并不掌握在英伟达手里。在这种情况下，拥抱而不是排斥x86，对老黄来说是最理性的选择，而在x86生态里，目前性价比最高的选项就是与英特尔合作了。

Build and run everything from simple web apps to AI supercomputing by matching each workload to the right Azure VM in minutes. Find and know exactly what you're provisioning by understanding the naming format to see CPU type, memory, storage, and features before deployment to match what your app or workload needs. Use free tools like Azure Migrate to right-size and plan. Matt McSpirit, Microsoft Azure expert, shows how to choose, size, and deploy workloads such as burstable web apps, massive in-memory databases, GPU-driven AI training, and high-performance scientific modeling, all with automatic scaling and confidential computing when needed. ► QUICK LINKS: 00:00 - Azure Virtual Machines 01:12 - Decode Azure VM Names 01:28 - Right-Size with Azure Migrate 02:15 - B series 02:45 - D series 03:23 - E series 04:14 - F series 04:29 - L series 05:01 - M series 05:23 - Constrained vCPU VMs 05:49 - H series 06:20 - N series 06:55 - Azure Boost 07:24 - Confidential VMs & Deploying your VMs 08:28 - Wrap up ► Link References Get started at https://aka.ms/VMAzure Azure VM naming conventions at https://aka.ms/VMnames ► Unfamiliar with Microsoft Mechanics? As Microsoft's official video series for IT, you can watch and share valuable content and demos of current and upcoming tech from the people who build it at Microsoft. • Subscribe to our YouTube: https://www.youtube.com/c/MicrosoftMechanicsSeries • Talk with other IT Pros, join us on the Microsoft Tech Community: https://techcommunity.microsoft.com/t5/microsoft-mechanics-blog/bg-p/MicrosoftMechanicsBlog • Watch or listen from anywhere, subscribe to our podcast: https://microsoftmechanics.libsyn.com/podcast ► Keep getting this insider knowledge, join us on social: • Follow us on Twitter: https://twitter.com/MSFTMechanics • Share knowledge on LinkedIn: https://www.linkedin.com/company/microsoft-mechanics/ • Enjoy us on Instagram: https://www.instagram.com/msftmechanics/ • Loosen up with us on TikTok: https://www.tiktok.com/@msftmechanics

This week on the podcast we go over our review of the KLEVV CRAS V RGB DDR5-6000 32GB Memory Kit.  We also discuss some interesting new CPU releases including the Ryzen 5 5600F and Core i5-110, Nintendo bringing back the Virtual Boy, new PC cases, and much more!

Markus Will, heise-online-Chefredakteur Dr. Volker Zota und Malte Kirchner sprechen in dieser Ausgabe der #heiseshow unter anderem über folgende Themen: - Wero statt Euro? Sparkassen wollen nicht auf EZB warten – Die deutschen Sparkassen setzen verstärkt auf das europäische Bezahlsystem Wero und wollen nicht länger auf den digitalen Euro der Europäischen Zentralbank warten. Das System soll europäischen Banken helfen, ihre Unabhängigkeit von internationalen Zahlungsdienstleistern zu stärken. Kann Wero als europäische Alternative zu PayPal und Co. langfristig bestehen? Welche Vorteile hätte ein schneller Wero-Rollout gegenüber dem Warten auf den digitalen Euro? Wie realistisch ist es, dass sich ein rein europäisches Bezahlsystem gegen die etablierte Konkurrenz durchsetzt? - Chip-Überraschung: Was der Einstieg von Nvidia bei Intel bedeutet- Nvidia steigt bei Intel ein und plant gemeinsame Produkte. Damit werden zwei Erzrivalen überraschend zu Partnern. Warum investiert Nvidia 5 Milliarden Dollar in Intel und was bedeutet diese unerwartete Allianz für die Zukunft der Prozessor-Landschaft? Welche Auswirkungen hat diese Allianz auf AMDs Position im CPU- und GPU-Markt? Und welche regulatorischen Hürden könnten bei einer solchen Milliardeninvestition zwischen Tech-Giganten auftreten? - 40 Jahre Super Mario: Jump'n'Run-Klempner ließ nicht nur Herzen höher hüpfen – Super Mario Bros. feiert seinen 40. Geburtstag und kann auf eine beispiellose Erfolgsgeschichte zurückblicken. Der italienische Klempner revolutionierte nicht nur das Jump'n'Run-Genre, sondern prägte die gesamte Videospielbranche nachhaltig. Was macht Mario nach vier Jahrzehnten immer noch so erfolgreich? Wie hat die Figur die Entwicklung der Videospielbranche beeinflusst? Welche Innovation war für den dauerhaften Erfolg der Mario-Spiele entscheidend? Außerdem wieder mit dabei: ein Nerd-Geburtstag, das WTF der Woche und knifflige Quizfragen.

Markus Will, heise-online-Chefredakteur Dr. Volker Zota und Malte Kirchner sprechen in dieser Ausgabe der #heiseshow unter anderem über folgende Themen: - Wero statt Euro? Sparkassen wollen nicht auf EZB warten – Die deutschen Sparkassen setzen verstärkt auf das europäische Bezahlsystem Wero und wollen nicht länger auf den digitalen Euro der Europäischen Zentralbank warten. Das System soll europäischen Banken helfen, ihre Unabhängigkeit von internationalen Zahlungsdienstleistern zu stärken. Kann Wero als europäische Alternative zu PayPal und Co. langfristig bestehen? Welche Vorteile hätte ein schneller Wero-Rollout gegenüber dem Warten auf den digitalen Euro? Wie realistisch ist es, dass sich ein rein europäisches Bezahlsystem gegen die etablierte Konkurrenz durchsetzt? - Chip-Überraschung: Was der Einstieg von Nvidia bei Intel bedeutet- Nvidia steigt bei Intel ein und plant gemeinsame Produkte. Damit werden zwei Erzrivalen überraschend zu Partnern. Warum investiert Nvidia 5 Milliarden Dollar in Intel und was bedeutet diese unerwartete Allianz für die Zukunft der Prozessor-Landschaft? Welche Auswirkungen hat diese Allianz auf AMDs Position im CPU- und GPU-Markt? Und welche regulatorischen Hürden könnten bei einer solchen Milliardeninvestition zwischen Tech-Giganten auftreten? - 40 Jahre Super Mario: Jump'n'Run-Klempner ließ nicht nur Herzen höher hüpfen – Super Mario Bros. feiert seinen 40. Geburtstag und kann auf eine beispiellose Erfolgsgeschichte zurückblicken. Der italienische Klempner revolutionierte nicht nur das Jump'n'Run-Genre, sondern prägte die gesamte Videospielbranche nachhaltig. Was macht Mario nach vier Jahrzehnten immer noch so erfolgreich? Wie hat die Figur die Entwicklung der Videospielbranche beeinflusst? Welche Innovation war für den dauerhaften Erfolg der Mario-Spiele entscheidend? Außerdem wieder mit dabei: ein Nerd-Geburtstag, das WTF der Woche und knifflige Quizfragen.

Ruby core team member Aaron Patterson (tenderlove) takes us deep into the cutting edge of Ruby's performance frontier in this technical exploration of how one of the world's most beloved programming languages continues to evolve.At Shopify, Aaron works on two transformative projects: ZJIT, a method-based JIT compiler that builds on YJIT's success by optimizing register allocation to reduce memory spills, and enhanced Ractor support to enable true CPU parallelism in Ruby applications. He explains the fundamental differences between these approaches - ZJIT makes single CPU utilization more efficient, while Ractors allow Ruby code to run across multiple CPUs simultaneously.The conversation reveals how real business needs drive language development. Shopify's production workloads unpredictably alternate between CPU-bound and IO-bound tasks, creating resource utilization challenges. Aaron's team aims to build auto-scaling web server infrastructure using Ractors that can dynamically adjust to workload characteristics - potentially revolutionizing how Ruby applications handle variable traffic patterns.For developers interested in contributing to Rails, Aaron offers practical advice: start reading the source code, understand the architecture, and look for ways to improve it. He shares insights on the challenges of making Rails Ractor-safe, particularly around passing lambdas between Ractors while maintaining memory safety.The episode concludes with a delightful tangent into Aaron's latest hardware project - building a color temperature sensor for camera calibration that combines his photography hobby with his programming expertise. True to form, even his leisure activities inevitably transform into coding projects.Whether you're a seasoned Ruby developer or simply curious about language design and performance optimization, Aaron's unique blend of deep technical knowledge and playful enthusiasm makes this an engaging journey through Ruby's exciting future.Send us some love. HoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.JudoscaleAutoscaling that actually works. Take control of your cloud hosting.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Support the show

Francois Daost is a W3C staff member and co-chair of the Web Developer Experience Community Group. We discuss the W3C's role and what it's like to go through the browser standardization process. Related links W3C TC39 Internet Engineering Task Force Web Hypertext Application Technology Working Group (WHATWG) Horizontal Groups Alliance for Open Media What is MPEG-DASH? | HLS vs. DASH Information about W3C and Encrypted Media Extensions (EME) Widevine PlayReady Media Source API Encrypted Media Extensions API requestVideoFrameCallback() Business Benefits of the W3C Patent Policy web.dev Baseline Portable Network Graphics Specification Internet Explorer 6 CSS Vendor Prefix WebRTC Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: today I'm talking to Francois Daoust. He's a staff member at the W3C. And we're gonna talk about the W3C and the recommendation process and discuss, Francois's experience with, with how these features end up in our browsers. [00:00:16] Jeremy: So, Francois, welcome [00:00:18] Francois: Thank you Jeremy and uh, many thanks for the invitation. I'm really thrilled to be part of this podcast. What's the W3C? [00:00:26] Jeremy: I think many of our listeners will have heard about the W3C, but they may not actually know what it is. So could you start by explaining what it is? [00:00:37] Francois: Sure. So W3C stands for the Worldwide Web Consortium. It's a standardization organization. I guess that's how people should think about W3C. it was created in 1994. I, by, uh, Tim Berners Lee, who was the inventor of the web. Tim Berners Lee was the, director of W3C for a long, long time. [00:01:00] Francois: He retired not long ago, a few years back. and W3C is, has, uh, a number of, uh. Properties, let's say first the goal is to produce royalty free standards, and that's very important. Uh, we want to make sure that, uh, the standard that get produced can be used and implemented without having to pay, fees to anyone. [00:01:23] Francois: We do web standards. I didn't mention it, but it's from the name. Standards that you find in your web browsers. But not only that, there are a number of other, uh, standards that got developed at W3C including, for example, XML. Data related standards. W3C as an organization is a consortium. [00:01:43] Francois: The, the C stands for consortium. Legally speaking, it's a, it's a 501c3 meaning in, so it's a US based, uh, legal entity not for profit. And the, the little three is important because it means it's public interest. That means we are a consortium, that means we have members, but at the same time, the goal, the mission is to the public. [00:02:05] Francois: So we're not only just, you know, doing what our members want. We are also making sure that what our members want is aligned with what end users in the end, need. and the W3C has a small team. And so I'm part of this, uh, of this team worldwide. Uh, 45 to 55 people, depending on how you count, mostly technical people and some, uh, admin, uh, as well, overseeing the, uh, the work, that we do, uh, at the W3C. Funding through membership fees [00:02:39] Jeremy: So you mentioned there's 45 to 55 people. How is this funded? Is this from governments or commercial companies? [00:02:47] Francois: The main source comes from membership fees. So the W3C has a, so members, uh, roughly 350 members, uh, at the W3C. And, in order to become a member, an organization needs to pay, uh, an annual membership fee. That's pretty common among, uh, standardization, uh, organizations. [00:03:07] Francois: And, we only have, uh, I guess three levels of membership, fees. Uh, well, you may find, uh, additional small levels, but three main ones. the goal is to make sure that, A big player will, not a big player or large company, will not have more rights than, uh, anything, anyone else. So we try to make sure that a member has the, you know, all members have equal, right? [00:03:30] Francois: if it's not perfect, but, uh, uh, that's how things are, are are set. So that's the main source of income for the W3C. And then we try to diversify just a little bit to get, uh, for example, we go to governments. We may go to governments in the u EU. We may, uh, take some, uh, grant for EU research projects that allow us, you know, to, study, explore topics. [00:03:54] Francois: Uh, in the US there, there used to be some, uh, some funding from coming from the government as well. So that, that's, uh, also, uh, a source. But the main one is, uh, membership fees. Relations to TC39, IETF, and WHATWG [00:04:04] Jeremy: And you mentioned that a lot of the W3C'S work is related to web standards. There's other groups like TC 39, which works on the JavaScript spec and the IETF, which I believe worked, with your group on WebRTC, I wonder if you could explain W3C'S connection to other groups like that. [00:04:28] Francois: sure. we try to collaborate with a, a number of, uh, standard other standardization organizations. So in general, everything goes well because you, you have, a clear separation of concerns. So you mentioned TC 39. Indeed. they are the ones who standardize, JavaScript. Proper name of JavaScript is the EcmaScript. [00:04:47] Francois: So that's tc. TC 39 is the technical committee at ecma. and so we have indeed interactions with them because their work directly impact the JavaScript that you're going to find in your, uh, run in your, in your web browser. And we develop a number of JavaScript APIs, uh, actually in W3C. [00:05:05] Francois: So we need to make sure that, the way we develop, uh, you know, these APIs align with the, the language itself. with IETF, the, the, the boundary is, uh, uh, is clear as well. It's a protocol and protocol for our network protocols for our, the IETF and application level. For W3C, that's usually how the distinction is made. [00:05:28] Francois: The boundaries are always a bit fuzzy, but that's how things work. And usually, uh, things work pretty well. Uh, there's also the WHATWG, uh, and the WHATWG is more the, the, the history was more complicated because, uh, t of a fork of the, uh, HTML specification, uh, at the time when it was developed by W3C, a long time ago. [00:05:49] Francois: And there was been some, uh, Well disagreement on the way things should have been done, and the WHATWG took over got created, took, took this the HTML spec and did it a different way. Went in another, another direction, and that other, other direction actually ended up being the direction. [00:06:06] Francois: So, that's a success, uh, from there. And so, W3C no longer works, no longer owns the, uh, HTML spec and the WHATWG has, uh, taken, uh, taken up a number of, uh, of different, core specifications for the web. Uh, doing a lot of work on the, uh, on interopoerability and making sure that, uh, the algorithm specified by the spec, were correct, which, which was something that historically we haven't been very good at at W3C. [00:06:35] Francois: And the way they've been working as a, has a lot of influence on the way we develop now, uh, the APIs, uh, from a W3C perspective. [00:06:44] Jeremy: So, just to make sure I understand correctly, you have TC 39, which is focused on the JavaScript or ECMAScript language itself, and you have APIs that are going to use JavaScript and interact with JavaScript. So you need to coordinate there. The, the have the specification for HTML. then the IATF, they are, I'm not sure if the right term would be, they, they would be one level lower perhaps, than the W3C. [00:07:17] Francois: That's how you, you can formulate it. Yes. The, the one layer, one layer layer in the ISO network in the ISO stack at the network level. How WebRTC spans the IETF and W3C [00:07:30] Jeremy: And so in that case, one place I've heard it mentioned is that webRTC, to, to use it, there is an IETF specification, and then perhaps there's a W3C recommendation and [00:07:43] Francois: Yes. so when we created the webRTC working group, that was in 2011, I think, it was created with a dual head. There was one RTC web, group that got created at IETF and a webRTC group that got created at W3C. And that was done on purpose. Of course, the goal was not to compete on the, on the solution, but actually to, have the two sides of the, uh, solution, be developed in parallel, the API, uh, the application front and the network front. [00:08:15] Francois: And there was a, and there's still a lot of overlap in, uh, participation between both groups, and that's what keep things successful. In the end. It's not, uh, you know, process or organization to organization, uh, relationships, coordination at the organization level. It's really the fact that you have participants that are essentially the same, on both sides of the equation. [00:08:36] Francois: That helps, uh, move things forward. Now, webRTC is, uh, is more complex than just one group at IETF. I mean, web, webRTC is a very complex set of, uh, of technologies, stack of technologies. So when you, when you. Pull a little, uh, protocol from IETFs. Suddenly you have the whole IETF that comes with you with it. [00:08:56] Francois: So you, it's the, you have the feeling that webRTC needs all of the, uh, internet protocols that got, uh, created to work Recommendations [00:09:04] Jeremy: And I think probably a lot of web developers, they may hear words like specification or standard, but I believe the, the official term, at least at the W3C, is this recommendation. And so I wonder if you can explain what that means. [00:09:24] Francois: Well. It means it means standard in the end. and that came from industry. That comes from a time where. As many standardization organizations. W3C was created not to be a standardization organization. It was felt that standard was not the right term because we were not a standardization organization. [00:09:45] Francois: So recommend IETF has the same thing. They call it RFC, request for comment, which, you know, stands for nothing in, and yet it's a standard. So W3C was created with the same kind of, uh thing. We needed some other terminology and we call that recommendation. But in the end, that's standard. It's really, uh, how you should see it. [00:10:08] Francois: And one thing I didn't mention when I, uh, introduced the W3C is there are two types of standards in the end, two main categories. There are, the de jure standards and defacto standards, two families. The de jure standards are the ones that are imposed by some kind of regulation. so it's really usually a standard you see imposed by governments, for example. [00:10:29] Francois: So when you look at your electric plug at home, there's some regulation there that says, this plug needs to have these properties. And that's a standard that gets imposed. It's a de jure standard. and then there are defacto standards which are really, uh, specifications that are out there and people agree to use it to implement it. [00:10:49] Francois: And by virtue of being used and implemented and used by everyone, they become standards. the, W3C really is in the, uh, second part. It's a defacto standard. IETF is the same thing. some of our standards are used in, uh, are referenced in regulations now, but, just a, a minority of them, most of them are defacto standards. [00:11:10] Francois: and that's important because that's in the end, it doesn't matter what the specific specification says, even though it's a bit confusing. What matters is that the, what the specifications says matches what implementations actually implement, and that these implementations are used, and are used interoperably across, you know, across browsers, for example, or across, uh, implementations, across users, across usages. [00:11:36] Francois: So, uh, standardization is a, is a lengthy process. The recommendation is the final stage in that, lengthy process. More and more we don't really reach recommendation anymore. If you look at, uh, at groups, uh, because we have another path, let's say we kind of, uh, we can stop at candidate recommendation, which is in theoretically a step before that. [00:12:02] Francois: But then you, you can stay there and, uh, stay there forever and publish new candidate recommendations. Um, uh, later on. What matters again is that, you know, you get this, virtuous feedback loop, uh, with implementers, and usage. [00:12:18] Jeremy: So if the candidate recommendation ends up being implemented by all the browsers, what's ends up being the distinction between a candidate and one that's a normal recommendation. [00:12:31] Francois: So, today it's mostly a process thing. Some groups actually decide to go to rec Some groups decide to stay at candidate rec and there's no formal difference between the, the two. we've made sure we've adopted, adjusted the process so that the important bits that, applied at the recommendation level now apply at the candidate rec level. Royalty free patent access [00:13:00] Francois: And by important things, I mean the patent commitments typically, uh, the patent policy fully applies at the candidate recommendation level so that you get your, protection, the royalty free patent protection that we, we were aiming at. [00:13:14] Francois: Some people do not care, you know, but most of the world still works with, uh, with patents, uh, for good, uh, or bad reasons. But, uh, uh, that's how things work. So we need to make, we're trying to make sure that we, we secure the right set of, um, of patent commitments from the right set of stakeholders. [00:13:35] Jeremy: Oh, so when someone implements a W3C recommendation or a candidate recommendation, the patent holders related to that recommendation, they basically agree to allow royalty-free use of that patent. [00:13:54] Francois: They do the one that were involved in the working group, of course, I mean, we can't say anything about the companies out there that may have patents and uh, are not part of this standardization process. So there's always, It's a remaining risk. but part of the goal when we create a working group is to make sure that, people understand the scope. [00:14:17] Francois: Lawyers look into it, and the, the legal teams that exist at the all the large companies, basically gave a green light saying, yeah, we, we we're pretty confident that we, we know where the patterns are on this particular, this particular area. And we are fine also, uh, letting go of the, the patterns we own ourselves. Implementations are built in parallel with standardization [00:14:39] Jeremy: And I think you had mentioned. What ends up being the most important is that the browser creators implement these recommendations. So it sounds like maybe the distinction between candidate recommendation and recommendation almost doesn't matter as long as you get the end result you want. [00:15:03] Francois: So, I mean, people will have different opinions, uh, in the, in standardization circles. And I mentioned also W3C is working on other kind of, uh, standards. So, uh, in some other areas, the nuance may be more important when we, but when, when you look at specification, that's target, web browsers. we've switched from a model where, specs were developed first and then implemented to a model where specs and implementing implementations are being, worked in parallel. [00:15:35] Francois: This actually relates to the evolution I was mentioning with the WHATWG taking over the HTML and, uh, focusing on the interoperability issues because the starting point was, yeah, we have an HTML 4.01 spec, uh, but it's not interoperable because it, it's not specified, are number of areas that are gray areas, you can implement them differently. [00:15:59] Francois: And so there are interoperable issues. Back to candidate rec actually, the, the, the, the stage was created, if I remember correctly. uh, if I'm, if I'm not wrong, the stage was created following the, uh, IE problem. In the CSS working group, IE6, uh, shipped with some, version of a CSS that was in the, as specified, you know, the spec was saying, you know, do that for the CSS box model. [00:16:27] Francois: And the IE6 was following that. And then the group decided to change, the box model and suddenly IE6 was no longer compliant. And that created a, a huge mess on the, in the history of, uh, of the web in a way. And so the, we, the, the, the, the candidate recommendation sta uh, stage was introduced following that to try to catch this kind of problems. [00:16:52] Francois: But nowadays, again, we, we switch to another model where it's more live. and so we, you, you'll find a number of specs that are not even at candidate rec level. They are at the, what we call a working draft, and they, they are being implemented, and if all goes well, the standardization process follows the implementation, and then you end up in a situation where you have your candidate rec when the, uh, spec ships. [00:17:18] Francois: a recent example would be a web GPU, for example. It, uh, it has shipped in, uh, in, in Chrome shortly before it transition to a candidate rec. But the, the, the spec was already stable. and now it's shipping uh, in, uh, in different browsers, uh, uh, safari, uh, and uh, and uh, and uh, Firefox. And so that's, uh, and that's a good example of something that follows, uh, things, uh, along pretty well. But then you have other specs such as, uh, in the media space, uh, request video frame back, uh, frame, call back, uh, requestVideoFrameCallback() is a short API that allows you to get, you know, a call back whenever the, the browser renders a video frame, essentially. [00:18:01] Francois: And that spec is implemented across browsers. But from a W3C specific, perspective, it does not even exist. It's not on the standardization track. It's still being incubated in what we call a community group, which is, you know, some something that, uh, usually exists before. we move to the, the standardization process. [00:18:21] Francois: So there, there are examples of things where some things fell through the cracks. All the standardization process, uh, is either too early or too late and things that are in spec are not exactly what what got implemented or implementations are too early in the process. We we're doing a better job, at, Not falling into a trap where someone ships, uh, you know, an implementation and then suddenly everything is frozen. You can no longer, change it because it's too late, it shipped. we've tried, different, path there. Um, mentioned CSS, the, there was this kind of vendor prefixed, uh, properties that used to be, uh, the way, uh, browsers were deploying new features without, you know, taking the final name. [00:19:06] Francois: We are trying also to move away from it because same thing. Then in the end, you end up with, uh, applications that have, uh, to duplicate all the properties, the CSS properties in the style sheets with, uh, the vendor prefixes and nuances in the, in what it does in, in the end. [00:19:23] Jeremy: Yeah, I, I think, is that in CSS where you'll see --mozilla or things like that? Why requestVideoFrameCallback doesn't have a formal specification [00:19:30] Jeremy: The example of the request video frame callback. I, I wonder if you have an opinion or, or, or know why that ended up the way it did, where the browsers all implemented it, even though it was still in the incubation stage. [00:19:49] Francois: On this one, I don't have a particular, uh, insights on whether there was a, you know, a strong reason to implement it,without doing the standardization work. [00:19:58] Francois: I mean, there are, it's not, uh, an IPR (Intellectual Property Rights) issue. It's not, uh, something that, uh, I don't think the, the, the spec triggers, uh, you know, problems that, uh, would be controversial or whatever. [00:20:10] Francois: Uh, so it's just a matter of, uh, there was no one's priority, and in the end, you end up with a, everyone's happy. it's, it has shipped. And so now doing the spec work is a bit,why spend time on something that's already shipped and so on, but the, it may still come back at some point with try to, you know, improve the situation. [00:20:26] Jeremy: Yeah, that's, that's interesting. It's a little counterintuitive because it sounds like you have the, the working group and it, it sounds like perhaps the companies or organizations involved, they maybe agreed on how it should work, and maybe that agreement almost made it so that they felt like they didn't need to move forward with the specification because they came to consensus even before going through that. [00:20:53] Francois: In this particular case, it's probably because it's really, again, it's a small, spec. It's just one function call, you know? I mean, they will definitely want a working group, uh, for larger specifications. by the way, actually now I know re request video frame call back. It's because the, the, the final goal now that it's, uh, shipped, is to merge it into, uh, HTML, uh, the HTML spec. [00:21:17] Francois: So there's a, there's an ongoing issue on the, the WHATWG side to integrate request video frame callback. And it's taking some time but see, it's, it's being, it, it caught up and, uh, someone is doing the, the work to, to do it. I had forgotten about this one. Um, [00:21:33] Jeremy: Tension from specification review (horizontal review) [00:21:33] Francois: so with larger specifications, organizations will want this kind of IPR regime they will want commit commitments from, uh, others, on the scope, on the process, on everything. So they will want, uh, a larger, a, a more formal setting, because that's part of how you ensure that things, uh, will get done properly. [00:21:53] Francois: I didn't mention it, but, uh, something we're really, uh, Pushy on, uh, W3C I mentioned we have principles, we have priorities, and we have, uh, specific several, uh, properties at W3C. And one of them is that we we're very strong on horizontal reviews of our specs. We really want them to be reviewed from an accessibility perspective, from an internationalization perspective, from a privacy and security, uh, perspective, and, and, and a technical architecture perspective as well. [00:22:23] Francois: And that's, these reviews are part of the formal process. So you, all specs need to undergo these reviews. And from time to time, that creates tension. Uh, from time to time. It just works, you know. Goes without problem. a recurring issue is that, privacy and security are hard. I mean, it's not an easy problem, something that can be, uh, solved, uh, easily. [00:22:48] Francois: Uh, so there's a, an ongoing tension and no easy way to resolve it, but there's an ongoing tension between, specifying powerful APIs and preserving privacy without meaning, not exposing too much information to applications in the media space. You can think of the media capabilities, API. So the media space is a complicated space. [00:23:13] Francois: Space because of codecs. codecs are typically not relative free. and so browsers decide which codecs they're going to support, which audio and video codecs they, they're going to support and doing that, that creates additional fragmentation, not in the sense that they're not interoperable, but in the sense that applications need to choose which connect they're going to ship to stream to the end user. [00:23:39] Francois: And, uh, it's all the more complicated that some codecs are going to be hardware supported. So you will have a hardware decoder in your, in your, in your laptop or smartphone. And so that's going to be efficient to decode some, uh, some stream, whereas some code are not, are going to be software, based, supported. [00:23:56] Francois: Uh, and that may consume a lot of CPU and a lot of power and a lot of energy in the end. So you, you want to avoid that if you can, uh, select another thing. Even more complex than, codecs have different profiles, uh, lower end profiles higher end profiles with different capabilities, different features, uh, depending on whether you're going to use this or that color space, for example, this or that resolution, whatever. [00:24:22] Francois: And so you want to surface that to web applications because otherwise, they can't. Select, they can't choose, the right codec and the right, stream that they're going to send to the, uh, client devices. And so they're not going to provide an efficient user experience first, and even a sustainable one in terms of energy because they, they're going to waste energy if they don't send the right stream. [00:24:45] Francois: So you want to surface that to application. That's what the media, media capabilities, APIs, provides. Privacy concerns [00:24:51] Francois: Uh, but at the same time, if you expose that information, you end up with ways to fingerprint the end user's device. And that in turn is often used to track users across, across sites, which is exactly what we don't want to have, uh, for privacy reasons, for obvious privacy reasons. [00:25:09] Francois: So you have to balance that and find ways to, uh, you know, to expose. Capabilities without, without necessarily exposing them too much. Uh, [00:25:21] Jeremy: Can you give an example of how some of those discussions went? Like within the working group? Who are the companies or who are the organizations that are arguing for We shouldn't have this capability because of the privacy concerns, or [00:25:40] Francois: In a way all of the companies, have a vision of, uh, of privacy. I mean, the, you will have a hard time finding, you know, members saying, I don't care about privacy. I just want the feature. Uh, they all have privacy in mind, but they may have a different approach to privacy. [00:25:57] Francois: so if you take, uh, let's say, uh, apple and Google would be the, the, I guess the perfect examples in that, uh, in that space, uh, Google will have a, an approach that is more open-ended thing. The, the user agents has this, uh, should check what the, the, uh, given site is doing. And then if it goes beyond, you know, some kind of threshold, they're going to say, well, okay, well, we'll stop exposing data to that, to that, uh, to that site. [00:26:25] Francois: So that application. So monitor and react in a way. apple has a more, uh, you know, has a stricter view on, uh, on privacy, let's say. And they will say, no, we, the, the, the feature must not exist in the first place. Or, but that's, I mean, I guess, um, it's not always that extreme. And, uh, from time to time it's the opposite. [00:26:45] Francois: You will have, uh, you know, apple arguing in one way, uh, which is more open-ended than the, uh, than, uh, than Google, for example. And they are not the only ones. So in working groups, uh, you will find the, usually the implementers. Uh, so when we talk about APIs that get implemented in browsers, you want the core browsers to be involved. [00:27:04] Francois: Uh, otherwise it's usually not a good sign for, uh, the success of the, uh, of the technology. So in practice, that means Apple, uh, Microsoft, Mozilla which one did I forget? [00:27:15] Jeremy: Google. [00:27:16] Francois: I forgot Google. Of course. Thank you. that's, uh, that the, the core, uh, list of participants you want to have in any, uh, group that develops web standards targeted at web browsers. Who participates in working groups and how much power do they have? [00:27:28] Francois: And then on top of that, you want, organizations and people who are directly going to use it, either because they, well the content providers. So in media, for example, if you look at the media working group, you'll see, uh, so browser vendors, the ones I mentioned, uh, content providers such as the BBC or Netflix. [00:27:46] Francois: Chip set vendors would, uh, would be there as well. Intel, uh, Nvidia again, because you know, there's a hardware decoding in there and encoding. So media is, touches on, on, uh, on hardware, uh, device manufacturer in general. You may, uh, I think, uh, I think Sony is involved in the, in the media working group, for example. [00:28:04] Francois: and these companies are usually less active in the spec development. It depends on the groups, but they're usually less active because the ones developing the specs are usually the browser again, because as I mentioned, we develop the specs in parallel to browsers implementing it. So they have the. [00:28:21] Francois: The feedback on how to formulate the, the algorithms. and so that's this collection of people who are going to discuss first within themselves. W3C pushes for consensual dis decisions. So we hardly take any votes in the working groups, but from time to time, that's not enough. [00:28:41] Francois: And there may be disagreements, but let's say there's agreement in the group, uh, when the spec matches. horizontal review groups will look at the specs. So these are groups I mentioned, accessibility one, uh, privacy, internationalization. And these groups, usually the participants are, it depends. [00:29:00] Francois: It can be anything. It can be, uh, the same companies. It can be, but usually different people from the same companies. But it the, maybe organizations with a that come from very, a very different angle. And that's a good thing because that means the, you know, you enlarge the, the perspectives on your, uh, on the, on the technology. [00:29:19] Francois: and you, that's when you have a discussion between groups, that takes place. And from time to time it goes well from time to time. Again, it can trigger issues that are hard to solve. and the W3C has a, an escalation process in case, uh, you know, in case things degenerate. Uh, starting with, uh, the notion of formal objection. [00:29:42] Jeremy: It makes sense that you would have the, the browser. Vendors and you have all the different companies that would use that browser. All the different horizontal groups like you mentioned, the internationalization, accessibility. I would imagine that you were talking about consensus and there are certain groups or certain companies that maybe have more say or more sway. [00:30:09] Jeremy: For example, if you're a browser, manufacturer, your Google. I'm kind of curious how that works out within the working group. [00:30:15] Francois: Yes, it's, I guess I would be lying if I were saying that, uh, you know, all companies are strictly equal in a, in a, in a group. they are from a process perspective, I mentioned, you know, different membership fees with were design, special specific ethos so that no one could say, I'm, I'm putting in a lot of money, so you, you need to re you need to respect me, uh, and you need to follow what I, what I want to, what I want to do. [00:30:41] Francois: at the same time, if you take a company like, uh, like Google for example, they send, hundreds of engineers to do standardization work. That's absolutely fantastic because that means work progresses and it's, uh, extremely smart people. So that's, uh, that's really a pleasure to work with, uh, with these, uh, people. [00:30:58] Francois: But you need to take a step back and say, well, the problem is. Defacto that gives them more power just by virtue of, uh, injecting more resources into it. So having always someone who can respond to an issue, having always someone, uh, editing a spec defacto that give them more, uh, um, more say on the, on the directions that, get forward. [00:31:22] Francois: And on top of that, of course, they have the, uh, I guess not surprisingly, the, the browser that is, uh, used the most, currently, on the market so there's a little bit of a, the, the, we, we, we, we try very hard to make sure that, uh, things are balanced. it's not a perfect world. [00:31:38] Francois: the the role of the team. I mean, I didn't talk about the role of the team, but part of it is to make sure that. Again, all perspectives are represented and that there's not, such a, such big imbalance that, uh, that something is wrong and that we really need to look into it. so making sure that anyone, if they have something to say, make making sure that they are heard by the rest of the group and not dismissed. [00:32:05] Francois: That usually goes well. There's no problem with that. And again, the escalation process I mentioned here doesn't make any, uh, it doesn't make any difference between, uh, a small player, a large player, a big player, and we have small companies raising formal objections against some of our aspects that happens, uh, all large ones. [00:32:24] Francois: But, uh, that happens too. There's no magical solution, I guess you can tell it by the way. I, uh, I don't know how to formulate the, the process more. It's a human process, and that's very important that it remains a human process as well. [00:32:41] Jeremy: I suppose the role of, of staff and someone in your position, for example, is to try and ensure that these different groups are, are heard and it isn't just one group taking control of it. [00:32:55] Francois: That's part of the role, again, is to make sure that, uh, the, the process is followed. So the, I, I mean, I don't want to give the impression that the process controls everything in the groups. I mean, the, the, the groups are bound by the process, but the process is there to catch problems when they arise. [00:33:14] Francois: most of the time there are no problems. It's just, you know, again, participants talking to each other, talking with the rest of the community. Most of the work happens in public nowadays, in any case. So the groups work in public essentially through asynchronous, uh, discussions on GitHub repositories. [00:33:32] Francois: There are contributions from, you know, non group participants and everything goes well. And so the process doesn't kick in. You just never say, eh, no, you didn't respect the process there. You, you closed the issue. You shouldn't have a, it's pretty rare that you have to do that. Uh, things just proceed naturally because they all, everyone understands where they are, why, what they're doing, and why they're doing it. [00:33:55] Francois: we still have a role, I guess in the, in the sense that from time to time that doesn't work and you have to intervene and you have to make sure that,the, uh, exception is caught and, uh, and processed, uh, in the right way. Discussions are public on github [00:34:10] Jeremy: And you said this process is asynchronous in public, so it sounds like someone, I, I mean, is this in GitHub issues or how, how would somebody go and, and see what the results of [00:34:22] Francois: Yes, there, there are basically a gazillion of, uh, GitHub repositories under the, uh, W3C, uh, organization on GitHub. Most groups are using GitHub. I mean, there's no, it's not mandatory. We don't manage any, uh, any tooling. But the factors that most, we, we've been transitioning to GitHub, uh, for a number of years already. [00:34:45] Francois: Uh, so that's where the work most of the work happens, through issues, through pool requests. Uh, that's where. people can go and raise issues against specifications. Uh, we usually, uh, also some from time to time get feedback from developers and countering, uh, a bug in a particular implementations, which we try to gently redirect to, uh, the actual bug trackers because we're not responsible for the respons implementations of the specs unless the spec is not clear. [00:35:14] Francois: We are responsible for the spec itself, making sure that the spec is clear and that implementers well, understand how they should implement something. Why the W3C doesn't specify a video or audio codec [00:35:25] Jeremy: I can see how people would make that mistake because they, they see it's the feature, but that's not the responsibility of the, the W3C to implement any of the specifications. Something you had mentioned there's the issue of intellectual property rights and how when you have a recommendation, you require the different organizations involved to make their patents available to use freely. [00:35:54] Jeremy: I wonder why there was never any kind of, recommendation for audio or video codecs in browsers since you have certain ones that are considered royalty free. But, I believe that's never been specified. [00:36:11] Francois: At W3C you mean? Yes. we, we've tried, I mean, it's not for lack of trying. Um, uh, we've had a number of discussions with, uh, various stakeholders saying, Hey, we, we really need, an audio or video code for our, for the web. the, uh, png PNG is an example of a, um, an image format which got standardized at W3C and it got standardized at W3C similar reasons. There had to be a royalty free image format for the web, and there was none at the time. of course, nowadays, uh, jpeg, uh, and gif or gif, whatever you call it, are well, you know, no problem with them. But, uh, um, that at the time P PNG was really, uh, meant to address this issue and it worked for PNG for audio and video. [00:37:01] Francois: We haven't managed to secure, commitments by stakeholders. So willingness to do it, so it's not, it's not lack of willingness. We would've loved to, uh, get, uh, a royalty free, uh, audio codec, a royalty free video codec again, audio and video code are extremely complicated because of this. [00:37:20] Francois: not only because of patterns, but also because of the entire business ecosystem that exists around them for good reasons. You, in order for a, a codec to be supported, deployed, effective, it really needs, uh, it needs to mature a lot. It needs to, be, uh, added to at a hardware level, to a number of devices, capturing devices, but also, um, uh, uh, of course players. [00:37:46] Francois: And that takes a hell of a lot of time and that's why you also enter a number of business considerations with business contracts between entities. so I'm personally, on a personal level, I'm, I'm pleased to see, for example, the Alliance for Open Media working on, uh, uh, AV1, uh, which is. At least they, uh, they wanted to be royalty free and they've been adopting actually the W3C patent policy to do this work. [00:38:11] Francois: So, uh, we're pleased to see that, you know, they've been adopting the same process and same thing. AV1 is not yet at the same, support stage, as other, codecs, in the world Yeah, I mean in devices. There's an open question as what, what are we going to do, uh, in the future uh, with that, it's, it's, it's doubtful that, uh, the W3C will be able to work on a, on a royalty free audio, codec or royalty free video codec itself because, uh, probably it's too late now in any case. [00:38:43] Francois: but It's one of these angles in the, in the web platform where we wish we had the, uh, the technology available for, for free. And, uh, it's not exactly, uh, how things work in practice.I mean, the way codecs are developed remains really patent oriented. [00:38:57] Francois: and you will find more codecs being developed. and that's where geopolitics can even enter the, the, uh, the play. Because, uh, if you go to China, you will find new codecs emerging, uh, that get developed within China also, because, the other codecs come mostly from the US so it's a bit of a problem and so on. [00:39:17] Francois: I'm not going to enter details and uh, I would probably say stupid things in any case. Uh, but that, uh, so we continue to see, uh, emerging codecs that are not royalty free, and it's probably going to remain the case for a number of years. unfortunately, unfortunately, from a W3C perspective and my perspective of course. [00:39:38] Jeremy: There's always these new, formats coming out and the, rate at which they get supported in the browser, even on a per browser basis is, is very, there can be a long time between, for example, WebP being released and a browser supporting it. So, seems like maybe we're gonna be in that situation for a while where the codecs will come out and maybe the browsers will support them. Maybe they won't, but the, the timeline is very uncertain. Digital Rights Management (DRM) and Media Source Extensions [00:40:08] Jeremy: Something you had, mentioned, maybe this was in your, email to me earlier, but you had mentioned that some of these specifications, there's, there's business considerations like with, digital rights management and, media source extensions. I wonder if you could talk a little bit about maybe what media source extensions is and encrypted media extensions and, and what the, the considerations or challenges are there. [00:40:33] Francois: I'm going to go very, very quickly over the history of a, video and audio support on the web. Initially it was supported through plugins. you are maybe too young to, remember that. But, uh, we had extensions, added to, uh, a realplayer. [00:40:46] Francois: This kind of things flash as well, uh, supporting, uh, uh, videos, in web pages, but it was not provided by the web browsers themselves. Uh, then HTML5 changed the, the situation. Adding these new tags, audio and video, but that these tags on this, by default, support, uh, you give them a resources, a resource, like an image as it's an audio or a video file. [00:41:10] Francois: They're going to download this, uh, uh, video file or audio file, and they're going to play it. That works well. But as soon as you want to do any kind of real streaming, files are too large and to stream, to, to get, you know, to get just a single fetch on, uh, on them. So you really want to stream them chunk by chunk, and you want to adapt the resolution at which you send the stream based on real time conditions of the user's network. [00:41:37] Francois: If there's plenty of bandwidth you want to send the user, the highest possible resolution. If there's a, some kind of hiccup temporary in the, in the network, you really want to lower the resolution, and that's called adaptive streaming. And to get adaptive streaming on the web, well, there are a number of protocols that exist. [00:41:54] Francois: Same thing. Some many of them are proprietary and actually they remain proprietary, uh, to some extent. and, uh, some of them are over http and they are the ones that are primarily used in, uh, in web contexts. So DASH comes to mind, DASH for Dynamic Adaptive streaming over http. HLS is another one. Uh, initially developed by Apple, I believe, and it's, uh, HTTP live streaming probably. Exactly. And, so there are different protocols that you can, uh, you can use. Uh, so the goal was not to standardize these protocols because again, there were some proprietary aspects to them. And, uh, same thing as with codecs. [00:42:32] Francois: There was no, well, at least people wanted to have the, uh, flexibility to tweak parameters, adaptive streaming parameters the way they wanted for different scenarios. You may want to tweak the parameters differently. So they, they needed to be more flexibility on top of protocols not being truly available for use directly and for implementation directly in browsers. [00:42:53] Francois: It was also about providing applications with, uh, the flexibility they would need to tweak parameters. So media source extensions comes into play for exactly that. Media source extensions is really about you. The application fetches chunks of its audio and video stream the way it wants, and with the parameters it wants, and it adjusts whatever it wants. [00:43:15] Francois: And then it feeds that into the, uh, video or audio tag. and the browser takes care of the rest. So it's really about, doing, you know, the adaptive streaming. let applications do it, and then, uh, let the user agent, uh, the browser takes, take care of the rendering itself. That's media source extensions. [00:43:32] Francois: Initially it was pushed by, uh, Netflix. They were not the only ones of course, but there, there was a, a ma, a major, uh, proponent of this, uh, technical solution, because they wanted, uh, they, uh, they were, expanding all over the world, uh, with, uh, plenty of native, applications on all sorts of, uh, of, uh, devices. [00:43:52] Francois: And they wanted to have a way to stream content on the web as well. both for both, I guess, to expand to, um, a new, um, ecosystem, the web, uh, providing new opportunities, let's say. But at the same time also to have a fallback, in case they, because for native support on different platforms, they sometimes had to enter business agreements with, uh, you know, the hardware manufacturers, the whatever, the, uh, service provider or whatever. [00:44:19] Francois: and so that was a way to have a full back. That kind of work is more open, in case, uh, things take some time and so on. So, and they probably had other reasons. I mean, I'm not, I can't speak on behalf of Netflix, uh, on others, but they were not the only ones of course, uh, supporting this, uh, me, uh, media source extension, uh, uh, specification. [00:44:42] Francois: and that went kind of, well, I think it was creating 2011. I mean, the, the work started in 2011 and the recommendation was published in 2016, which is not too bad from a standardization perspective. It means only five years, you know, it's a very short amount of time. Encrypted Media Extensions [00:44:59] Francois: At the same time, and in parallel and complement to the media source extension specifications, uh, there was work on the encrypted media extensions, and here it was pushed by the same proponent in a way because they wanted to get premium content on the web. [00:45:14] Francois: And by premium content, you think of movies and, uh. These kind of beasts. And the problem with the, I guess the basic issue with, uh, digital asset such as movies, is that they cost hundreds of millions to produce. I mean, some cost less of course. And yet it's super easy to copy them if you have a access to the digital, uh, file. [00:45:35] Francois: You just copy and, uh, and that's it. Piracy uh, is super easy, uh, to achieve. It's illegal of course, but it's super easy to do. And so that's where the different legislations come into play with digital right management. Then the fact is most countries allow system that, can encrypt content and, uh, through what we call DRM systems. [00:45:59] Francois: so content providers, uh, the, the ones that have movies, so the studios here more, more and more, and Netflix is one, uh, one of the studios nowadays. Um, but not only, not only them all major studios will, uh, would, uh, push for, wanted to have something that would allow them to stream encrypted content, encrypted audio and video, uh, mostly video, to, uh, to web applications so that, uh, you. [00:46:25] Francois: Provide the movies, otherwise, they, they are just basically saying, and sorry, but, uh, this premium content will never make it to the web because there's no way we're gonna, uh, send it in clear, to, uh, to the end user. So Encrypting media extensions is, uh, is an API that allows to interface with, uh, what's called the content decryption module, CDM, uh, which itself interacts with, uh, the DR DRM systems that, uh, the browser may, may or may not support. [00:46:52] Francois: And so it provides a way for an application to receive encrypted content, pass it over get the, the, the right keys, the right license keys from a whatever system actually. Pass that logic over to the, and to the user agent, which passes, passes it over to, uh, the CDM system, which is kind of black box in, uh, that does its magic to get the right, uh, decryption key and then the, and to decrypt the content that can be rendered. [00:47:21] Francois: The encrypted media extensions triggered a, a hell of a lot of, uh, controversy. because it's DRM and DRM systems, uh, many people, uh, uh, things should be banned, uh, especially on the web because the, the premise of the web is that the, the user has trusts, a user agent. The, the web browser is called the user agent in all our, all our specifications. [00:47:44] Francois: And that's, uh, that's the trust relationship. And then they interact with a, a content provider. And so whatever they do with the content is their, I guess, actually their problem. And DRM introduces a third party, which is, uh, there's, uh, the, the end user no longer has the control on the content. [00:48:03] Francois: It has to rely on something else that, Restricts what it can achieve with the content. So it's, uh, it's not only a trust relationship with its, uh, user agents, it's also with, uh, with something else, which is the content provider, uh, in the end, the one that has the, uh, the license where provides the license. [00:48:22] Francois: And so that's, that triggers, uh, a hell of a lot of, uh, of discussions in the W3C degenerated, uh, uh, into, uh, formal objections being raised against the specification. and that escalated to, to the, I mean, at all leverage it. It's, it's the, the story in, uh, W3C that, um, really, uh, divided the membership into, opposed camps in a way, if you, that's was not only year, it was not really 50 50 in the sense that not just a huge fights, but the, that's, that triggered a hell of a lot of discussions and a lot of, a lot of, uh, of formal objections at the time. [00:49:00] Francois: Uh, we were still, From a governance perspective, interestingly, um, the W3C used to be a dictatorship. It's not how you should formulate it, of course, and I hope it's not going to be public, this podcast. Uh, but the, uh, it was a benevolent dictatorship. You could see it this way in the sense that, uh, the whole process escalated to one single person was, Tim Burners Lee, who had the final say, on when, when none of the other layers, had managed to catch and to resolve, a conflict. [00:49:32] Francois: Uh, that has hardly ever happened in, uh, the history of the W3C, but that happened to the two for EME, for encrypted media extensions. It had to go to the, uh, director level who, uh, after due consideration, uh, decided to, allow the EME to proceed. and that's why we have a, an EME, uh, uh, standard right now, but still re it remains something on the side. [00:49:56] Francois: EME we're still, uh, it's still in the scope of the media working group, for example. but the scope, if you look at the charter of the working group, we try to scope the, the, the, the, the updates we can make to the specification, uh, to make sure that we don't reopen, reopen, uh, a can of worms, because, well, it's really a, a topic that triggers friction for good and bad reasons again. [00:50:20] Jeremy: And when you talk about the media source extensions, that is the ability to write custom code to stream video in whatever way you want. You mentioned, the MPEG-DASH and http live streaming. So in that case, would that be the developer gets to write that code in JavaScript that's executed by the browser? [00:50:43] Francois: Yep, that's, uh, that would be it. and then typically, I guess the approach nowadays is more and more to develop low level APIs into W3C or web in, in general, I guess. And to let, uh. Libraries emerge that are going to make lives of a, a developer, uh, easier. So for MPEG DASH, we have the DASH.js, which does a fantastic job at, uh, at implementing the complexity of, uh, of adaptive streaming. [00:51:13] Francois: And you just, you just hook it into your, your workflow. And that's, uh, and that's it. Encrypted Media Extensions are closed source [00:51:20] Jeremy: And with the encrypted media extensions I'm trying to picture how those work and how they work differently. [00:51:28] Francois: Well, it's because the, the, the, the key architecture is that the, the stream that you, the stream that you may assemble with a media source extensions, for example. 'cause typically they, they're used in collaboration. When you hook the, hook it into the video tag, you also. Call EME and actually the stream goes to EME. [00:51:49] Francois: And when it goes to EME, actually the user agent hands the encrypted stream. You're still encrypted at this time. Uh, encrypted, uh, stream goes to the CDM content decryption module, and that's a black box well, it has some black, black, uh, black box logic. So it's not, uh, even if you look at the chromium source code, for example, you won't see the implementation of the CDM because it's a, it's a black box, so it's not part of the browser se it's a sand, it's sandboxed, it's execution sandbox. [00:52:17] Francois: That's, uh, the, the EME is kind of unique in, in this way where the, the CDM is not allowed to make network requests, for example, again, for privacy reasons. so anyway, the, the CDM box has the logic to decrypt the content and it hands it over, and then it depends, it depends on the level of protection you. [00:52:37] Francois: You need or that the system supports. It can be against software based protection, in which case actually, a highly motivated, uh, uh, uh, attacker could, uh, actually get access to the decoded stream, or it can be more hardware protected, in which case actually the, it goes to the, uh, to your final screen. [00:52:58] Francois: But it goes, it, it goes through the hardware in a, in a mode that the US supports in a mode that even the user agent doesn't have access to it. So it doesn't, it can't even see the pixels that, uh, gets rendered on the screen. There are, uh, several other, uh, APIs that you could use, for example, to take a screenshot of your, of your application and so on. [00:53:16] Francois: And you cannot apply them to, uh, such content because they're just gonna return a black box. again, because the user agent itself does not see the, uh, the pixels, which is exactly what you want with encrypted content. [00:53:29] Jeremy: And the, the content decryption module, it's, if I understand correctly, it's something that's shipped with the browsers, but you were saying is if you were to look at the public source code of Chromium or of Firefox, you would not see that implementation. Content Decryption Module (Widevine, PlayReady) [00:53:47] Francois: True. I mean, the, the, um, the typical examples are, uh, uh, widevine, so wide Vine. So interestingly, uh, speaking in theory, these, uh, systems could have been provided by anyone in practice. They've been provided by the browser vendors themselves. So Google has Wide Vine. Uh, Microsoft has something called PlayReady. Apple uh, the name, uh, escapes my, uh, sorry. They don't have it on top of my mind. So they, that's basically what they support. So they, they also own that code, but in a way they don't have to. And Firefox actually, uh, they, uh, don't, don't remember which one, they support among these three. but, uh, they, they don't own that code typically. [00:54:29] Francois: They provide a wrapper around, around it. Yeah, that's, that's exactly the, the crux of the, uh, issue that, people have with, uh, with DRMs, right? It's, uh, the fact that, uh, suddenly you have a bit of code running there that is, uh, that, okay, you can send box, but, uh, you cannot inspect and you don't have, uh, access to its, uh, source code. [00:54:52] Jeremy: That's interesting. So the, almost the entire browser is open source, but if you wanna watch a Netflix movie for example, then you, you need to, run this, this CDM, in addition to just the browser code. I, I think, you know, we've kind of covered a lot. Documenting what's available in browsers for developers [00:55:13] Jeremy: I wonder if there's any other examples or anything else you thought would be important to mention in, in the context of the W3C. [00:55:23] Francois: There, there's one thing which, uh, relates to, uh, activities I'm doing also at W3C. Um. Here, we've been talking a lot about, uh, standards and, implementations in browsers, but there's also, uh, adoption of these browser, of these technology standards by developers in general and making sure that developers are aware of what exists, making sure that they understand what exists and one of the, key pain points that people, uh. [00:55:54] Francois: Uh, keep raising on, uh, the web platform is first. Well, the, the, the web platform is unique in the sense that there are different implementations. I mean, if you, [00:56:03] Francois: Uh, anyway, there are different, uh, context, different run times where there, there's just one provided by the company that owns the, uh, the, the, the system. The web platform is implemented by different, uh, organizations. and so you end up the system where no one, there's what's in the specs is not necessarily supported. [00:56:22] Francois: And of course, MDN tries, uh, to document what's what's supported, uh, thoroughly. But for MDN to work, there's a hell of a lot of needs for data that, tracks browser support. And this, uh, this data is typically in a project called the Browser Compat Data, BCD owned by, uh, MDN as well. But, the Open Web Docs collective is a, uh, is, uh, the one, maintaining that, uh, that data under the hoods. [00:56:50] Francois: anyway, all of that to say that, uh, to make sure that, we track things beyond work on technical specifications, because if you look at it from W3C perspective, life ends when the spec reaches standards, uh, you know, candidate rec or rec, you could just say, oh, done with my work. but that's not how things work. [00:57:10] Francois: There's always, you need the feedback loop and, in order to make sure that developers get the information and can provide the, the feedback that standardization can benefit from and browser vendors can benefit from. We've been working on a project called web Features with browser vendors mainly, and, uh, a few of the folks and MDN and can I use and different, uh, different people, to catalog, the web in terms of features that speak to developers and from that catalog. [00:57:40] Francois: So it's a set of, uh, it's a set of, uh, feature IDs with a feature name and feature description that say, you know, this is how developers would, uh, understand, uh, instead of going too fine grained in terms of, uh, there's this one function call that does this because that's where you, the, the kind of support data you may get from browser data and MDN initially, and having some kind of a coarser grained, uh, structure that says these are the, features that make sense. [00:58:09] Francois: They talk to developers. That's what developers talk about, and that's the info. So the, we need to have data on these particular features because that's how developers are going approach the specs. Uh. and from that we've derived the notion of baseline badges that you have, uh, are now, uh, shown on MDN on can I use and integrated in, uh, IDE tool, IDE Tools such as visual, visual studio, and, uh, uh, libraries, uh, linked, some linters have started to, um, to integrate that data. [00:58:41] Francois: Uh, so, the way it works is, uh, we've been mapping these coarser grained features to BCDs finer grained support data, and from there we've been deriving a kind of a, a batch that says, yeah, this, this feature is implemented well, has limited availability because it's only implemented in one or two browsers, for example. [00:59:07] Francois: It's, newly available because. It was implemented. It's been, it's implemented across the main browser vendor, um, across the main browsers that people use. But it's recent, and widely available, which we try to, uh, well, there's been lots of discussion in the, in the group to, uh, come up with a definition which essentially ends up being 30 months after, a feature become, became newly available. [00:59:34] Francois: And that's when, that's the time it takes for the, for the versions of the, the different versions of the browser to propagate. Uh, because you, it's not because there's a new version of a, of a browser that, uh, people just, Ima immediately, uh, get it. So it takes a while, to propagate, uh, across the, uh, the, the user, uh, user base. [00:59:56] Francois: And so the, the goal is to have a, a, a signal that. Developers can rely on saying, okay, well it's widely available so I can really use that feature. And of course, if that doesn't work, then we need to know about it. And so we are also working with, uh, people doing so developer surveys such as state of, uh, CSS, state of HTML, state of JavaScript. [01:00:15] Francois: That's I guess, the main ones. But also we are also running, uh, MDN short surveys with the MDN people to gather feedback on. On the, on these same features, and to feed the loop and to, uh, to complete the loop. and these data is also used by, internally, by browser vendors to inform, prioritization process, their prioritization process, and typically as part of the interop project that they're also running, uh, on the site [01:00:43] Francois: So a, a number of different, I've mentioned, uh, I guess a number of different projects, uh, coming along together. But that's the goal is to create links, across all of these, um, uh, ongoing projects with a view to integrating developers, more, and gathering feedback as early as possible and inform decision. [01:01:04] Francois: We take at the standardization level that can affect the, the lives of the developers and making sure that it's, uh, it affects them in a, in a positive way. [01:01:14] Jeremy: just trying to understand, 'cause you had mentioned that there's the web features and the baseline, and I was, I was trying to picture where developers would actually, um, see these things. And it sounds like from what you're saying is W3C comes up with what stage some of these features are at, and then developers would end up seeing it on MDN or, or some other site. [01:01:37] Francois: So, uh, I'm working on it, but that doesn't mean it's a W3C thing. It's a, it's a, again, it's a, we have different types of group. It's a community group, so it's the Web DX Community group at W3C, which means it's a community owned thing. so that's why I'm mentioning a working with a representative from, and people from MDN people, from open Web docs. [01:02:05] Francois: so that's the first point. The second point is, so it's, indeed this data is now being integrated. If you, and you look, uh, you'll, you'll see it in on top of the MDN pages on most of them. If you look at, uh, any kind of feature, you'll see a, a few logos, uh, a baseline banner. and then can I use, it's the same thing. [01:02:24] Francois: You're going to get a baseline, banner. It's more on, can I use, and it's meant to capture the fact that the feature is widely available or if you may need to pay attention to it. Of course, it's a simplification, and the goal is not to the way it's, the way the messaging is done to developers is meant to capture the fact that, they may want to look, uh, into more than just this, baseline status, because. [01:02:54] Francois: If you take a look at web platform tests, for example, and if you were to base your assessment of whether a feature is supported based on test results, you'll end up saying the web platform has no supported technology because there are absolutely no API that, uh, where browsers pass 100% of the, of the, of the test suite. [01:03:18] Francois: There may be a few of them, I don't know. But, there's a simplification in the, in the process when a feature is, uh, set to be baseline, there may be more things to look at nevertheless, but it's meant to provide a signal that, uh, still developers can rely on their day-to-day, uh, lives. [01:03:36] Francois: if they use the, the feature, let's say, as a reasonably intended and not, uh, using to advance the logic. [01:03:48] Jeremy: I see. Yeah. I'm looking at one of the pages on MDN right now, and I can see at the top there's the, the baseline and it, it mentions that this feature works across many browsers and devices, and then they say how long it's been available. And so that's a way that people at a glance can, can tell, which APIs they can use. [01:04:08] Francois: it also started, uh, out of a desire to summarize this, uh, browser compatibility table that you see at the end of the page of the, the bottom of the page in on MDN. but there are where developers were saying, well, it's, it's fine, but it's, it goes too much into detail. So we don't know in the end, can we, can we use that feature or can we, can we not use that feature? [01:04:28] Francois: So it's meant as a informed summary of, uh, of, of that it relies on the same data again. and more importantly, we're beyond MDN, we're working with tools providers to integrate that as well. So I mentioned the, uh, visual Studio is one of them. So recently they shipped a new version where when you use a feature, you can, you can have some contextual, uh. [01:04:53] Francois: A menu that tells you, yeah, uh, that's fine. You, this CSS property, you can, you can use it, it's widely available or be aware this one is limited Availability only, availability only available in Firefox or, or Chrome or Safari work kit, whatever. [01:05:08] Jeremy: I think that's a good place to wrap it up, if people want to learn more about the work you're doing or learn more about sort of this whole recommendations process, where, where should they head? [01:05:23] Francois: Generally speaking, we're extremely open to, uh, people contributing to the W3C. and where should they go if they, it depends on what they want. So I guess the, the in usually where, how things start for someone getting involved in the W3C is that they have some

Topics covered in this episode: * Mozilla's Lifeline is Safe After Judge's Google Antitrust Ruling* * troml - suggests or fills in trove classifiers for your projects* * pqrs: Command line tool for inspecting Parquet files* * Testing for Python 3.14* Extras Joke Watch on YouTube About the show Sponsored by us! Support our work through: Our courses at Talk Python Training The Complete pytest Course Patreon Supporters Connect with the hosts Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky) Brian: @brianokken@fosstodon.org / @brianokken.bsky.social Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Michael #1: Mozilla's Lifeline is Safe After Judge's Google Antitrust Ruling A judge lets Google keep paying Mozilla to make Google the default search engine but only if those deals aren't exclusive. More than 85% of Mozilla's revenue comes from Google search payments. The ruling forbids Google from making exclusive contracts for Search, Chrome, Google Assistant, or Gemini, and forces data sharing and search syndication so rivals get a fighting chance. Brian #2: troml - suggests or fills in trove classifiers for your projects Adam Hill This is super cool and so welcome. Trove Classifiers are things like Programming Language :: Python :: 3.14 that allow for some fun stuff to show up in PyPI, like the versions you support, etc. Note that just saying you require 3.9+ doesn't tell the user that you've actually tested stuff on 3.14. I like to keep Trove Classifiers around for this reason. Also, License classifier is deprecated, and if you include it, it shows up in two places, in Meta, and in the Classifiers section. Probably good to only have one place. So I'm going to be removing it from classifiers for my projects. One problem, classifier text has to be an exact match to something in the classifier list, so we usually recommend copy/pasting from that list. But no longer! Just use troml! It just fills it in for you (if you run troml suggest --fix). How totally awesome is that! I tried it on pytest-check, and it was mostly right. It suggested me adding 3.15, which I haven't tested yet, so I'm not ready to add that just yet. :) BTW, I talked with Brett Cannon about classifiers back in ‘23 if you want some more in depth info on trove classifiers. Michael #3: pqrs: Command line tool for inspecting Parquet files pqrs is a command line tool for inspecting Parquet files This is a replacement for the parquet-tools utility written in Rust Built using the Rust implementation of Parquet and Arrow pqrs roughly means "parquet-tools in rust" Why Parquet? Size A 200 MB CSV will usually shrink to somewhere between about 20-100 MB as Parquet depending on the data and compression. Loading a Parquet file is typically several times faster than parsing CSV, often 2x-10x faster for a full-file load and much faster when you only read some columns. Speed Full-file load into pandas: Parquet with pyarrow/fastparquet is usually 2x–10x faster than reading CSV with pandas because CSV parsing is CPU intensive (text tokenizing, dtype inference). Example: if read_csv is 10 seconds, read_parquet might be ~1–5 seconds depending on CPU and codec. Column subset: Parquet is much faster if you only need some columns — often 5x–50x faster because it reads only those column chunks. Predicate pushdown & row groups: When using dataset APIs (pyarrow.dataset) you can push filters to skip row groups, reducing I/O dramatically for selective queries. Memory usage: Parquet avoids temporary string buffers and repeated parsing, so peak memory and temporary allocations are often lower. Brian #4: Testing for Python 3.14 Python 3.14 is just around the corner, with a final release scheduled for October. What's new in Python 3.14 Python 3.14 release schedule Adding 3.14 to your CI tests in GitHub Actions Add “3.14” and optionally “3.14t” for freethreaded Add the line allow-prereleases: true I got stuck on this, and asked folks on Mastdon and Bluesky A couple folks suggested the allow-prereleases: true step. Thank you! Ed Rogers also suggested Hugo's article Free-threaded Python on GitHub Actions, which I had read and forgot about. Thanks Ed! And thanks Hugo! Extras Brian: dj-toml-settings : Load Django settings from a TOML file. - Another cool project from Adam Hill LidAngleSensor for Mac - from Sam Henri Gold, with examples of creaky door and theramin Listener Bryan Weber found a Python version via Changelog, pybooklid, from tcsenpai Grab PyBay Michael: Ready prek go! by Hugo van Kemenade Joke: Console Devs Can't Find a Date

In this podcast, Thomas Domville walks through Apple's new Adaptive Power mode in iOS, explaining what it does, which devices support it, what trade-offs to expect, and how to turn it on. You'll learn how the system uses on-device intelligence to detect unusually power-hungry apps or tasks and gently throttle performance to extend battery life—plus how this differs from the traditional Low Power Mode.What is Adaptive Power?An AI-assisted battery feature that watches for apps or tasks using more CPU/battery than usual and automatically makes performance adjustments (e.g., slightly dimming the display or allowing some activities to take longer) to reduce drain.It's conservative compared to Low Power Mode—only intervenes when something is actually hogging resources, so the phone behaves normally most of the time.Trade-offs: When Adaptive Power kicks in, you may notice subtle slowdowns (emails/messages can arrive a bit slower; animations feel slightly less snappy; display may dim a touch).Device support: Requires newer, AI-capable iPhone models (as referenced in the show).Key points & takeawaysSet-and-forget: Once enabled, it only activates when needed—otherwise your phone runs as usual.Notifications available: You can enable an Adaptive Power notification so you know when it's actively managing performance.Works alongside Low Power Mode: Low Power Mode remains the more aggressive option; Adaptive Power is a lighter-touch, smarter layer for everyday use.How to enable Adaptive PowerOpen Settings.Double Tap Battery.Double Tap Power Mode (near the bottom of the screen).Toggle Adaptive PowerOn.(Optional) Turn on Adaptive Power Notifications to be alerted when it activates.(Optional) Use Low Power Mode when you want a stronger, system-wide battery-saving profile (iOS will typically prompt you around 20% battery).VoiceOver tips (from the demo)In Settings, navigate by swiping right until you reach Battery, then double-tap.On the Battery screen, you can four-finger tap near the bottom to quickly reach elements closer to the end of the list, then flick left/right to Power Mode.Toggle Adaptive Power and Adaptive Power Notifications with a double-tap.When to use whichAdaptive Power: Daily driver—great for automatic, gentle savings without constantly changing how your phone feels.Low Power Mode: Use when you need maximum battery conservation (travel days, long events, low-battery emergencies).TranscriptDisclaimer: This transcript was generated by AI Note Taker – VoicePen, an AI-powered transcription app. It is not edited or formatted, and…

Katia, Emmanuel et Guillaume discutent Java, Kotlin, Quarkus, Hibernate, Spring Boot 4, intelligence artificielle (modèles Nano Banana, VO3, frameworks agentiques, embedding). On discute les vulnerabilités OWASP pour les LLMs, les personalités de codage des différents modèles, Podman vs Docker, comment moderniser des projets legacy. Mais surtout on a passé du temps sur les présentations de Luc Julia et les différents contre points qui ont fait le buzz sur les réseaux. Enregistré le 12 septembre 2025 Téléchargement de l'épisode LesCastCodeurs-Episode-330.mp3 ou en vidéo sur YouTube. News Langages Dans cette vidéo, José détaille les nouveautés de Java entre Java 21 et 25 https://inside.java/2025/08/31/roadto25-java-language/ Aperçu des nouveautés du JDK 25 : Introduction des nouvelles fonctionnalités du langage Java et des changements à venir [00:02]. Programmation orientée données et Pattern Matching [00:43] : Évolution du “pattern matching” pour la déconstruction des “records” [01:22]. Utilisation des “sealed types” dans les expressions switch pour améliorer la lisibilité et la robustesse du code [01:47]. Introduction des “unnamed patterns” (_) pour indiquer qu'une variable n'est pas utilisée [04:47]. Support des types primitifs dans instanceof et switch (en preview) [14:02]. Conception d'applications Java [00:52] : Simplification de la méthode main [21:31]. Exécution directe des fichiers .java sans compilation explicite [22:46]. Amélioration des mécanismes d'importation [23:41]. Utilisation de la syntaxe Markdown dans la Javadoc [27:46]. Immuabilité et valeurs nulles [01:08] : Problème d'observation de champs final à null pendant la construction d'un objet [28:44]. JEP 513 pour contrôler l'appel à super() et restreindre l'usage de this dans les constructeurs [33:29]. JDK 25 sort le 16 septembre https://openjdk.org/projects/jdk/25/ Scoped Values (JEP 505) - alternative plus efficace aux ThreadLocal pour partager des données immutables entre threads Structured Concurrency (JEP 506) - traiter des groupes de tâches concurrentes comme une seule unité de travail, simplifiant la gestion des threads Compact Object Headers (JEP 519) - Fonctionnalité finale qui réduit de 50% la taille des en-têtes d'objets (de 128 à 64 bits), économisant jusqu'à 22% de mémoire heap Flexible Constructor Bodies (JEP 513) - Relaxation des restrictions sur les constructeurs, permettant du code avant l'appel super() ou this() Module Import Declarations (JEP 511) - Import simplifié permettant d'importer tous les éléments publics d'un module en une seule déclaration Compact Source Files (JEP 512) - Simplification des programmes Java basiques avec des méthodes main d'instance sans classe wrapper obligatoire Primitive Types in Patterns (JEP 455) - Troisième preview étendant le pattern matching et instanceof aux types primitifs dans switch et instanceof Generational Shenandoah (JEP 521) - Le garbage collector Shenandoah passe en mode générationnel pour de meilleures performances JFR Method Timing & Tracing (JEP 520) - Nouvel outillage de profilage pour mesurer le temps d'exécution et tracer les appels de méthodes Key Derivation API (JEP 510) - API finale pour les fonctions de dérivation de clés cryptographiques, remplaçant les implémentations tierces Améliorations du traitement des annotations dans Kotlin 2.2 https://blog.jetbrains.com/idea/2025/09/improved-annotation-handling-in-kotlin-2-2-less-boilerplate-fewer-surprises/ Avant Kotlin 2.2, les annotations sur les paramètres de constructeur n'étaient appliquées qu'au paramètre, pas à la propriété ou au champ Cela causait des bugs subtils avec Spring et JPA où la validation ne fonctionnait qu'à la création d'objet, pas lors des mises à jour La solution précédente nécessitait d'utiliser explicitement @field: pour chaque annotation, créant du code verbeux Kotlin 2.2 introduit un nouveau comportement par défaut qui applique les annotations aux paramètres ET aux propriétés/champs automatiquement Le code devient plus propre sans avoir besoin de syntaxe @field: répétitive Pour l'activer, ajouter -Xannotation-default-target=param-property dans les options du compilateur Gradle IntelliJ IDEA propose un quick-fix pour activer ce comportement à l'échelle du projet Cette amélioration rend l'intégration Kotlin plus fluide avec les frameworks majeurs comme Spring et JPA Le comportement peut être configuré pour garder l'ancien mode ou activer un mode transitoire avec avertissements Cette mise à jour fait partie d'une initiative plus large pour améliorer l'expérience Kotlin + Spring Librairies Sortie de Quarkus 3.26 avec mises à jour d'Hibernate et autres fonctionnalités - https://quarkus.io/blog/quarkus-3-26-released/ mettez à jour vers la 3.26.x car il y a eu une regression vert.x Jalon important vers la version LTS 3.27 prévue fin septembre, basée sur cette version Mise à jour vers Hibernate ORM 7.1, Hibernate Search 8.1 et Hibernate Reactive 3.1 Support des unités de persistance nommées et sources de données dans Hibernate Reactive Démarrage hors ligne et configuration de dialecte pour Hibernate ORM même si la base n'est pas accessible Refonte de la console HQL dans Dev UI avec fonctionnalité Hibernate Assistant intégrée Exposition des capacités Dev UI comme fonctions MCP pour pilotage via outils IA Rafraîchissement automatique des tokens OIDC en cas de réponse 401 des clients REST Extension JFR pour capturer les données runtime (nom app, version, extensions actives) Bump de Gradle vers la version 9.0 par défaut, suppression du support des classes config legacy Guide de démarrage avec Quarkus et A2A Java SDK 0.3.0 (pour faire discuter des agents IA avec la dernière version du protocole A2A) https://quarkus.io/blog/quarkus-a2a-java-0-3-0-alpha-release/ Sortie de l'A2A Java SDK 0.3.0.Alpha1, aligné avec la spécification A2A v0.3.0. Protocole A2A : standard ouvert (Linux Foundation), permet la communication inter-agents IA polyglottes. Version 0.3.0 plus stable, introduit le support gRPC. Mises à jour générales : changements significatifs, expérience utilisateur améliorée (côté client et serveur). Agents serveur A2A : Support gRPC ajouté (en plus de JSON-RPC). HTTP+JSON/REST à venir. Implémentations basées sur Quarkus (alternatives Jakarta existent). Dépendances spécifiques pour chaque transport (ex: a2a-java-sdk-reference-jsonrpc, a2a-java-sdk-reference-grpc). AgentCard : décrit les capacités de l'agent. Doit spécifier le point d'accès primaire et tous les transports supportés (additionalInterfaces). Clients A2A : Dépendance principale : a2a-java-sdk-client. Support gRPC ajouté (en plus de JSON-RPC). HTTP+JSON/REST à venir. Dépendance spécifique pour gRPC : a2a-java-sdk-client-transport-grpc. Création de client : via ClientBuilder. Sélectionne automatiquement le transport selon l'AgentCard et la configuration client. Permet de spécifier les transports supportés par le client (withTransport). Comment générer et éditer des images en Java avec Nano Banana, le “photoshop killer” de Google https://glaforge.dev/posts/2025/09/09/calling-nano-banana-from-java/ Objectif : Intégrer le modèle Nano Banana (Gemini 2.5 Flash Image preview) dans des applications Java. SDK utilisé : GenAI Java SDK de Google. Compatibilité : Supporté par ADK for Java ; pas encore par LangChain4j (limitation de multimodalité de sortie). Capacités de Nano Banana : Créer de nouvelles images. Modifier des images existantes. Assembler plusieurs images. Mise en œuvre Java : Quelle dépendance utiliser Comment s'authentifier Comment configurer le modèle Nature du modèle : Nano Banana est un modèle de chat qui peut retourner du texte et une image (pas simplement juste un modèle générateur d'image) Exemples d'utilisation : Création : Via un simple prompt textuel. Modification : En passant l'image existante (tableau de bytes) et les instructions de modification (prompt). Assemblage : En passant plusieurs images (en bytes) et les instructions d'intégration (prompt). Message clé : Toutes ces fonctionnalités sont accessibles en Java, sans nécessiter Python. Générer des vidéos IA avec le modèle Veo 3, mais en Java ! https://glaforge.dev/posts/2025/09/10/generating-videos-in-java-with-veo3/ Génération de vidéos en Java avec Veo 3 (via le GenAI Java SDK de Google). Veo 3: Annoncé comme GA, prix réduits, support du format 9:16, résolution jusqu'à 1080p. Création de vidéos : À partir d'une invite textuelle (prompt). À partir d'une image existante. Deux versions différentes du modèle : veo-3.0-generate-001 (qualité supérieure, plus coûteux, plus lent). veo-3.0-fast-generate-001 (qualité inférieure, moins coûteux, mais plus rapide). Rod Johnson sur ecrire des aplication agentic en Java plus facilement qu'en python avec Embabel https://medium.com/@springrod/you-can-build-better-ai-agents-in-java-than-python-868eaf008493 Rod the papa de Spring réécrit un exemple CrewAI (Python) qui génère un livre en utilisant Embabel (Java) pour démontrer la supériorité de Java L'application utilise plusieurs agents AI spécialisés : un chercheur, un planificateur de livre et des rédacteurs de chapitres Le processus suit trois étapes : recherche du sujet, création du plan, rédaction parallèle des chapitres puis assemblage CrewAI souffre de plusieurs problèmes : configuration lourde, manque de type safety, utilisation de clés magiques dans les prompts La version Embabel nécessite moins de code Java que l'original Python et moins de fichiers de configuration YAML Embabel apporte la type safety complète, éliminant les erreurs de frappe dans les prompts et améliorant l'outillage IDE La gestion de la concurrence est mieux contrôlée en Java pour éviter les limites de débit des APIs LLM L'intégration avec Spring permet une configuration externe simple des modèles LLM et hyperparamètres Le planificateur Embabel détermine automatiquement l'ordre d'exécution des actions basé sur leurs types requis L'argument principal : l'écosystème JVM offre un meilleur modèle de programmation et accès à la logique métier existante que Python Il y a pas mal de nouveaux framework agentic en Java, notamment le dernier LAngchain4j Agentic Spring lance un serie de blog posts sur les nouveautés de Spring Boot 4 https://spring.io/blog/2025/09/02/road_to_ga_introduction baseline JDK 17 mais rebase sur Jakarta 11 Kotlin 2, Jackson 3 et JUnit 6 Fonctionnalités de résilience principales de Spring : @ConcurrencyLimit, @Retryable, RetryTemplate Versioning d'API dans Spring Améliorations du client de service HTTP L'état des clients HTTP dans Spring Introduction du support Jackson 3 dans Spring Consommateur partagé - les queues Kafka dans Spring Kafka Modularisation de Spring Boot Autorisation progressive dans Spring Security Spring gRPC - un nouveau module Spring Boot Applications null-safe avec Spring Boot 4 OpenTelemetry avec Spring Boot Repos Ahead of Time (Partie 2) Web Faire de la recherche sémantique directement dans le navigateur en local, avec EmbeddingGemma et Transformers.js https://glaforge.dev/posts/2025/09/08/in-browser-semantic-search-with-embeddinggemma/ EmbeddingGemma: Nouveau modèle d'embedding (308M paramètres) de Google DeepMind. Objectif: Permettre la recherche sémantique directement dans le navigateur. Avantages clés de l'IA côté client: Confidentialité: Aucune donnée envoyée à un serveur. Coûts réduits: Pas besoin de serveurs coûteux (GPU), hébergement statique. Faible latence: Traitement instantané sans allers-retours réseau. Fonctionnement hors ligne: Possible après le chargement initial du modèle. Technologie principale: Modèle: EmbeddingGemma (petit, performant, multilingue, support MRL pour réduire la taille des vecteurs). Moteur d'inférence: Transformers.js de HuggingFace (exécute les modèles AI en JavaScript dans le navigateur). Déploiement: Site statique avec Vite/React/Tailwind CSS, déployé sur Firebase Hosting via GitHub Actions. Gestion du modèle: Fichiers du modèle trop lourds pour Git; téléchargés depuis HuggingFace Hub pendant le CI/CD. Fonctionnement de l'app: Charge le modèle, génère des embeddings pour requêtes/documents, calcule la similarité sémantique. Conclusion: Démonstration d'une recherche sémantique privée, économique et sans serveur, soulignant le potentiel de l'IA embarquée dans le navigateur. Data et Intelligence Artificielle Docker lance Cagent, une sorte de framework multi-agent IA utilisant des LLMs externes, des modèles de Docker Model Runner, avec le Docker MCP Tookit. Il propose un format YAML pour décrire les agents d'un système multi-agents. https://github.com/docker/cagent des agents “prompt driven” (pas de code) et une structure pour decrire comment ils sont deployés pas clair comment ils sont appelés a part dans la ligne de commande de cagent fait par david gageot L'owasp décrit l'independance excessive des LLM comme une vulnerabilité https://genai.owasp.org/llmrisk2023-24/llm08-excessive-agency/ L'agence excessive désigne la vulnérabilité qui permet aux systèmes LLM d'effectuer des actions dommageables via des sorties inattendues ou ambiguës. Elle résulte de trois causes principales : fonctionnalités excessives, permissions excessives ou autonomie excessive des agents LLM. Les fonctionnalités excessives incluent l'accès à des plugins qui offrent plus de capacités que nécessaire, comme un plugin de lecture qui peut aussi modifier ou supprimer. Les permissions excessives se manifestent quand un plugin accède aux systèmes avec des droits trop élevés, par exemple un accès en lecture qui inclut aussi l'écriture. L'autonomie excessive survient quand le système effectue des actions critiques sans validation humaine préalable. Un scénario d'attaque typique : un assistant personnel avec accès email peut être manipulé par injection de prompt pour envoyer du spam via la boîte de l'utilisateur. La prévention implique de limiter strictement les plugins aux fonctions minimales nécessaires pour l'opération prévue. Il faut éviter les fonctions ouvertes comme “exécuter une commande shell” au profit d'outils plus granulaires et spécifiques. L'application du principe de moindre privilège est cruciale : chaque plugin doit avoir uniquement les permissions minimales requises. Le contrôle humain dans la boucle reste essentiel pour valider les actions à fort impact avant leur exécution. Lancement du MCP registry, une sorte de méta-annuaire officiel pour référencer les serveurs MCP https://www.marktechpost.com/2025/09/09/mcp-team-launches-the-preview-version-of-the-mcp-registry-a-federated-discovery-layer-for-enterprise-ai/ MCP Registry : Couche de découverte fédérée pour l'IA d'entreprise. Fonctionne comme le DNS pour le contexte de l'IA, permettant la découverte de serveurs MCP publics ou privés. Modèle fédéré : Évite les risques de sécurité et de conformité d'un registre monolithique. Permet des sous-registres privés tout en conservant une source de vérité “upstream”. Avantages entreprises : Découverte interne sécurisée. Gouvernance centralisée des serveurs externes. Réduction de la prolifération des contextes. Support pour les agents IA hybrides (données privées/publiques). Projet open source, actuellement en version preview. Blog post officiel : https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/ Exploration des internals du transaction log SQL Server https://debezium.io/blog/2025/09/08/sqlserver-tx-log/ C'est un article pour les rugeux qui veulent savoir comment SQLServer marche à l'interieur Debezium utilise actuellement les change tables de SQL Server CDC en polling périodique L'article explore la possibilité de parser directement le transaction log pour améliorer les performances Le transaction log est divisé en Virtual Log Files (VLFs) utilisés de manière circulaire Chaque VLF contient des blocs (512B à 60KB) qui contiennent les records de transactions Chaque record a un Log Sequence Number (LSN) unique pour l'identifier précisément Les données sont stockées dans des pages de 8KB avec header de 96 bytes et offset array Les tables sont organisées en partitions et allocation units pour gérer l'espace disque L'utilitaire DBCC permet d'explorer la structure interne des pages et leur contenu Cette compréhension pose les bases pour parser programmatiquement le transaction log dans un prochain article Outillage Les personalités des codeurs des différents LLMs https://www.sonarsource.com/blog/the-coding-personalities-of-leading-llms-gpt-5-update/ GPT-5 minimal ne détrône pas Claude Sonnet 4 comme leader en performance fonctionnelle malgré ses 75% de réussite GPT-5 génère un code extrêmement verbeux avec 490 000 lignes contre 370 000 pour Claude Sonnet 4 sur les mêmes tâches La complexité cyclomatique et cognitive du code GPT-5 est dramatiquement plus élevée que tous les autres modèles GPT-5 introduit 3,90 problèmes par tâche réussie contre seulement 2,11 pour Claude Sonnet 4 Point fort de GPT-5 : sécurité exceptionnelle avec seulement 0,12 vulnérabilité par 1000 lignes de code Faiblesse majeure : densité très élevée de “code smells” (25,28 par 1000 lignes) nuisant à la maintenabilité GPT-5 produit 12% de problèmes liés à la complexité cognitive, le taux le plus élevé de tous les modèles Tendance aux erreurs logiques fondamentales avec 24% de bugs de type “Control-flow mistake” Réapparition de vulnérabilités classiques comme les failles d'injection et de traversée de chemin Nécessité d'une gouvernance renforcée avec analyse statique obligatoire pour gérer la complexité du code généré Pourquoi j'ai abandonné Docker pour Podman https://codesmash.dev/why-i-ditched-docker-for-podman-and-you-should-too Problème Docker : Le daemon dockerd persistant s'exécute avec des privilèges root, posant des risques de sécurité (nombreuses CVEs citées) et consommant des ressources inutilement. Solution Podman : Sans Daemon : Pas de processus d'arrière-plan persistant. Les conteneurs s'exécutent comme des processus enfants de la commande Podman, sous les privilèges de l'utilisateur. Sécurité Renforcée : Réduction de la surface d'attaque. Une évasion de conteneur compromet un utilisateur non privilégié sur l'hôte, pas le système entier. Mode rootless. Fiabilité Accrue : Pas de point de défaillance unique ; le crash d'un conteneur n'affecte pas les autres. Moins de Ressources : Pas de daemon constamment actif, donc moins de mémoire et de CPU. Fonctionnalités Clés de Podman : Intégration Systemd : Génération automatique de fichiers d'unité systemd pour gérer les conteneurs comme des services Linux standards. Alignement Kubernetes : Support natif des pods et capacité à générer des fichiers Kubernetes YAML directement (podman generate kube), facilitant le développement local pour K8s. Philosophie Unix : Se concentre sur l'exécution des conteneurs, délègue les tâches spécialisées à des outils dédiés (ex: Buildah pour la construction d'images, Skopeo pour leur gestion). Migration Facile : CLI compatible Docker : podman utilise les mêmes commandes que docker (alias docker=podman fonctionne). Les Dockerfiles existants sont directement utilisables. Améliorations incluses : Sécurité par défaut (ports privilégiés en mode rootless), meilleure gestion des permissions de volume, API Docker compatible optionnelle. Option de convertir Docker Compose en Kubernetes YAML. Bénéfices en Production : Sécurité améliorée, utilisation plus propre des ressources. Podman représente une évolution plus sécurisée et mieux alignée avec les pratiques modernes de gestion Linux et de déploiement de conteneurs. Guide Pratique (Exemple FastAPI) : Le Dockerfile ne change pas. podman build et podman run remplacent directement les commandes Docker. Déploiement en production via Systemd. Gestion d'applications multi-services avec les “pods” Podman. Compatibilité Docker Compose via podman-compose ou kompose. Détection améliorée des APIs vulnérables dans les IDEs JetBrains et Qodana - https://blog.jetbrains.com/idea/2025/09/enhanced-vulnerable-api-detection-in-jetbrains-ides-and-qodana/ JetBrains s'associe avec Mend.io pour renforcer la sécurité du code dans leurs outils Le plugin Package Checker bénéficie de nouvelles données enrichies sur les APIs vulnérables Analyse des graphes d'appels pour couvrir plus de méthodes publiques des bibliothèques open-source Support de Java, Kotlin, C#, JavaScript, TypeScript et Python pour la détection de vulnérabilités Activation des inspections via Paramètres > Editor > Inspections en recherchant “Vulnerable API” Surlignage automatique des méthodes vulnérables avec détails des failles au survol Action contextuelle pour naviguer directement vers la déclaration de dépendance problématique Mise à jour automatique vers une version non affectée via Alt+Enter sur la dépendance Fenêtre dédiée “Vulnerable Dependencies” pour voir l'état global des vulnérabilités du projet Méthodologies Le retour de du sondage de Stack Overflow sur l'usage de l'IA dans le code https://medium.com/@amareshadak/stack-overflow-just-exposed-the-ugly-truth-about-ai-coding-tools-b4f7b5992191 84% des développeurs utilisent l'IA quotidiennement, mais 46% ne font pas confiance aux résultats. Seulement 3,1% font “hautement confiance” au code généré. 66% sont frustrés par les solutions IA “presque correctes”. 45% disent que déboguer le code IA prend plus de temps que l'écrire soi-même. Les développeurs seniors (10+ ans) font moins confiance à l'IA (2,6%) que les débutants (6,1%), créant un écart de connaissances dangereux. Les pays occidentaux montrent moins de confiance - Allemagne (22%), UK (23%), USA (28%) - que l'Inde (56%). Les créateurs d'outils IA leur font moins confiance. 77% des développeurs professionnels rejettent la programmation en langage naturel, seuls 12% l'utilisent réellement. Quand l'IA échoue, 75% se tournent vers les humains. 35% des visites Stack Overflow concernent maintenant des problèmes liés à l'IA. 69% rapportent des gains de productivité personnels, mais seulement 17% voient une amélioration de la collaboration d'équipe. Coûts cachés : temps de vérification, explication du code IA aux équipes, refactorisation et charge cognitive constante. Les plateformes humaines dominent encore : Stack Overflow (84%), GitHub (67%), YouTube (61%) pour résoudre les problèmes IA. L'avenir suggère un “développement augmenté” où l'IA devient un outil parmi d'autres, nécessitant transparence et gestion de l'incertitude. Mentorat open source et défis communautaires par les gens de Microcks https://microcks.io/blog/beyond-code-open-source-mentorship/ Microcks souffre du syndrome des “utilisateurs silencieux” qui bénéficient du projet sans contribuer Malgré des milliers de téléchargements et une adoption croissante, l'engagement communautaire reste faible Ce manque d'interaction crée des défis de durabilité et limite l'innovation du projet Les mainteneurs développent dans le vide sans feedback des vrais utilisateurs Contribuer ne nécessite pas de coder : documentation, partage d'expérience, signalement de bugs suffisent Parler du project qu'on aime autour de soi est aussi super utile Microcks a aussi des questions specifiques qu'ils ont posé dans le blog, donc si vous l'utilisez, aller voir Le succès de l'open source dépend de la transformation des utilisateurs en véritables partenaires communautaires c'est un point assez commun je trouve, le ratio parlant / silencieux est tres petit et cela encourage les quelques grandes gueules La modernisation du systemes legacy, c'est pas que de la tech https://blog.scottlogic.com/2025/08/27/holistic-approach-successful-legacy-modernisation.html Un artcile qui prend du recul sur la modernisation de systemes legacy Les projets de modernisation legacy nécessitent une vision holistique au-delà du simple focus technologique Les drivers business diffèrent des projets greenfield : réduction des coûts et mitigation des risques plutôt que génération de revenus L'état actuel est plus complexe à cartographier avec de nombreuses dépendances et risques de rupture Collaboration essentielle entre Architectes, Analystes Business et Designers UX dès la phase de découverte Approche tridimensionnelle obligatoire : Personnes, Processus et Technologie (comme un jeu d'échecs 3D) Le leadership doit créer l'espace nécessaire pour la découverte et la planification plutôt que presser l'équipe Communication en termes business plutôt que techniques vers tous les niveaux de l'organisation Planification préalable essentielle contrairement aux idées reçues sur l'agilité Séquencement optimal souvent non-évident et nécessitant une analyse approfondie des interdépendances Phases projet alignées sur les résultats business permettent l'agilité au sein de chaque phase Sécurité Cyber Attaque su Musée Histoire Naturelle https://www.franceinfo.fr/internet/securite-sur-internet/cyberattaques/le-museum-nati[…]e-d-une-cyberattaque-severe-une-plainte-deposee_7430356.html Compromission massive de packages npm populaires par un malware crypto https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised 18 packages npm très populaires compromis le 8 septembre 2025, incluant chalk, debug, ansi-styles avec plus de 2 milliards de téléchargements hebdomadaires combinés duckdb s'est rajouté à la liste Code malveillant injecté qui intercepte silencieusement l'activité crypto et web3 dans les navigateurs des utilisateurs Le malware manipule les interactions de wallet et redirige les paiements vers des comptes contrôlés par l'attaquant sans signes évidents Injection dans les fonctions critiques comme fetch, XMLHttpRequest et APIs de wallets (window.ethereum, Solana) pour intercepter le trafic Détection et remplacement automatique des adresses crypto sur multiple blockchains (Ethereum, Bitcoin, Solana, Tron, Litecoin, Bitcoin Cash) Les transactions sont modifiées en arrière-plan même si l'interface utilisateur semble correcte et légitime Utilise des adresses “sosies” via correspondance de chaînes pour rendre les échanges moins évidents à détecter Le mainteneur compromis par email de phishing provenant du faux domaine “mailto:support@npmjs.help|support@npmjs.help” enregistré 3 jours avant l'attaque sur une demande de mise a jour de son autheotnfication a deux facteurs après un an Aikido a alerté le mainteneur via Bluesky qui a confirmé la compromission et commencé le nettoyage des packages Attaque sophistiquée opérant à plusieurs niveaux: contenu web, appels API et manipulation des signatures de transactions Les anti-cheats de jeux vidéo : une faille de sécurité majeure ? - https://tferdinand.net/jeux-video-et-si-votre-anti-cheat-etait-la-plus-grosse-faille/ Les anti-cheats modernes s'installent au Ring 0 (noyau système) avec privilèges maximaux Ils obtiennent le même niveau d'accès que les antivirus professionnels mais sans audit ni certification Certains exploitent Secure Boot pour se charger avant le système d'exploitation Risque de supply chain : le groupe APT41 a déjà compromis des jeux comme League of Legends Un attaquant infiltré pourrait désactiver les solutions de sécurité et rester invisible Menace de stabilité : une erreur peut empêcher le démarrage du système (référence CrowdStrike) Conflits possibles entre différents anti-cheats qui se bloquent mutuellement Surveillance en temps réel des données d'utilisation sous prétexte anti-triche Dérive dangereuse selon l'auteur : des entreprises de jeux accèdent au niveau EDR Alternatives limitées : cloud gaming ou sandboxing avec impact sur performances donc faites gaffe aux jeux que vos gamins installent ! Loi, société et organisation Luc Julia au Sénat - Monsieur Phi réagi et publie la vidéo Luc Julia au Sénat : autopsie d'un grand N'IMPORTE QUOI https://www.youtube.com/watch?v=e5kDHL-nnh4 En format podcast de 20 minutes, sorti au même moment et à propos de sa conf à Devoxx https://www.youtube.com/watch?v=Q0gvaIZz1dM Le lab IA - Jérôme Fortias - Et si Luc Julia avait raison https://www.youtube.com/watch?v=KScI5PkCIaE Luc Julia au Senat https://www.youtube.com/watch?v=UjBZaKcTeIY Luc Julia se défend https://www.youtube.com/watch?v=DZmxa7jJ8sI Intelligence artificielle : catastrophe imminente ? - Luc Julia vs Maxime Fournes https://www.youtube.com/watch?v=sCNqGt7yIjo Tech and Co Monsieur Phi vs Luc Julia (put a click) https://www.youtube.com/watch?v=xKeFsOceT44 La tronche en biais https://www.youtube.com/live/zFwLAOgY0Wc Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 12 septembre 2025 : Agile Pays Basque 2025 - Bidart (France) 15 septembre 2025 : Agile Tour Montpellier - Montpellier (France) 18-19 septembre 2025 : API Platform Conference - Lille (France) & Online 22-24 septembre 2025 : Kernel Recipes - Paris (France) 22-27 septembre 2025 : La Mélée Numérique - Toulouse (France) 23 septembre 2025 : OWASP AppSec France 2025 - Paris (France) 23-24 septembre 2025 : AI Engineer Paris - Paris (France) 25 septembre 2025 : Agile Game Toulouse - Toulouse (France) 25-26 septembre 2025 : Paris Web 2025 - Paris (France) 30 septembre 2025-1 octobre 2025 : PyData Paris 2025 - Paris (France) 2 octobre 2025 : Nantes Craft - Nantes (France) 2-3 octobre 2025 : Volcamp - Clermont-Ferrand (France) 3 octobre 2025 : DevFest Perros-Guirec 2025 - Perros-Guirec (France) 6-7 octobre 2025 : Swift Connection 2025 - Paris (France) 6-10 octobre 2025 : Devoxx Belgium - Antwerp (Belgium) 7 octobre 2025 : BSides Mulhouse - Mulhouse (France) 7-8 octobre 2025 : Agile en Seine - Issy-les-Moulineaux (France) 8-10 octobre 2025 : SIG 2025 - Paris (France) & Online 9 octobre 2025 : DevCon #25 : informatique quantique - Paris (France) 9-10 octobre 2025 : Forum PHP 2025 - Marne-la-Vallée (France) 9-10 octobre 2025 : EuroRust 2025 - Paris (France) 16 octobre 2025 : PlatformCon25 Live Day Paris - Paris (France) 16 octobre 2025 : Power 365 - 2025 - Lille (France) 16-17 octobre 2025 : DevFest Nantes - Nantes (France) 17 octobre 2025 : Sylius Con 2025 - Lyon (France) 17 octobre 2025 : ScalaIO 2025 - Paris (France) 17-19 octobre 2025 : OpenInfra Summit Europe - Paris (France) 20 octobre 2025 : Codeurs en Seine - Rouen (France) 23 octobre 2025 : Cloud Nord - Lille (France) 30-31 octobre 2025 : Agile Tour Bordeaux 2025 - Bordeaux (France) 30-31 octobre 2025 : Agile Tour Nantais 2025 - Nantes (France) 30 octobre 2025-2 novembre 2025 : PyConFR 2025 - Lyon (France) 4-7 novembre 2025 : NewCrafts 2025 - Paris (France) 5-6 novembre 2025 : Tech Show Paris - Paris (France) 5-6 novembre 2025 : Red Hat Summit: Connect Paris 2025 - Paris (France) 6 novembre 2025 : dotAI 2025 - Paris (France) 6 novembre 2025 : Agile Tour Aix-Marseille 2025 - Gardanne (France) 7 novembre 2025 : BDX I/O - Bordeaux (France) 12-14 novembre 2025 : Devoxx Morocco - Marrakech (Morocco) 13 novembre 2025 : DevFest Toulouse - Toulouse (France) 15-16 novembre 2025 : Capitole du Libre - Toulouse (France) 19 novembre 2025 : SREday Paris 2025 Q4 - Paris (France) 19-21 novembre 2025 : Agile Grenoble - Grenoble (France) 20 novembre 2025 : OVHcloud Summit - Paris (France) 21 novembre 2025 : DevFest Paris 2025 - Paris (France) 27 novembre 2025 : DevFest Strasbourg 2025 - Strasbourg (France) 28 novembre 2025 : DevFest Lyon - Lyon (France) 1-2 décembre 2025 : Tech Rocks Summit 2025 - Paris (France) 4-5 décembre 2025 : Agile Tour Rennes - Rennes (France) 5 décembre 2025 : DevFest Dijon 2025 - Dijon (France) 9-11 décembre 2025 : APIdays Paris - Paris (France) 9-11 décembre 2025 : Green IO Paris - Paris (France) 10-11 décembre 2025 : Devops REX - Paris (France) 10-11 décembre 2025 : Open Source Experience - Paris (France) 11 décembre 2025 : Normandie.ai 2025 - Rouen (France) 14-17 janvier 2026 : SnowCamp 2026 - Grenoble (France) 2-6 février 2026 : Web Days Convention - Aix-en-Provence (France) 3 février 2026 : Cloud Native Days France 2026 - Paris (France) 12-13 février 2026 : Touraine Tech #26 - Tours (France) 22-24 avril 2026 : Devoxx France 2026 - Paris (France) 23-25 avril 2026 : Devoxx Greece - Athens (Greece) 17 juin 2026 : Devoxx Poland - Krakow (Poland) 4 septembre 2026 : JUG SUmmer Camp 2026 - La Rochelle (France) Nous contacter Pour réagir à cet épisode, venez discuter sur le groupe Google https://groups.google.com/group/lescastcodeurs Contactez-nous via X/twitter https://twitter.com/lescastcodeurs ou Bluesky https://bsky.app/profile/lescastcodeurs.com Faire un crowdcast ou une crowdquestion Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Tous les épisodes et toutes les infos sur https://lescastcodeurs.com/

Episode 81: We're back! Lots to discuss in this video, including YouTube weirdness, the future of AMD and Intel's CPU platforms, the good old CPU core debate, upcoming GPU rumors and more.CHAPTERS00:00 - Intro03:13 - Our YouTube views are down, this is what the stats say31:14 - Zen 7 on AM5 and Intel's competing platform54:13 - How important is platform longevity?1:07:58 - Six core CPUs are still powerful for gaming1:17:27 - Will Intel make an Arc B770?1:26:22 - No RTX Super any time soon1:29:14 - Updates from our boring livesSUBSCRIBE TO THE PODCASTAudio: https://shows.acast.com/the-hardware-unboxed-podcastVideo: https://www.youtube.com/channel/UCqT8Vb3jweH6_tj2SarErfwSUPPORT US DIRECTLYPatreon: https://www.patreon.com/hardwareunboxedLINKSYouTube: https://www.youtube.com/@Hardwareunboxed/Twitter: https://twitter.com/HardwareUnboxedBluesky: https://bsky.app/profile/hardwareunboxed.bsky.social Hosted on Acast. See acast.com/privacy for more information.

An airhacks.fm conversation with Ingo Kegel (@IngoKegel) about: jprofiler Visual Studio Code integration using Kotlin Multiplatform, migrating Java code to Kotlin common code for cross-platform compatibility, transpiling to JavaScript for Node.js runtime, JClassLib bytecode viewer and manipulation library, Visual Studio Code's Language Server Protocol (LSP), profiling unit tests and performance regression testing, Java Flight Recorder (JFR) for production monitoring with custom business events, cost-driven development in cloud environments, serverless architecture with AWS Lambda and S3, performance optimization with parallelism in single-CPU environments, integrating profiling data with LLMs for automated optimization, MCP servers for AI agent integration, Gradle and Maven build system integration, cooperative window switching between JProfiler and VS Code, memory profiling and thread analysis, comparing streams vs for-loops performance, brokk AI's Swing-based LLM development tool, context-aware performance analysis, automated code optimization with AI agents, business event correlation with low-level JVM metrics, cost estimation based on cloud API calls, quarkus for fast startup times in serverless, performance assertions in System Tests, multi-monitor development workflow support Ingo Kegel on twitter: @IngoKegel

Thunderstorms were raging across southern Germany as Elliot Williams was joined by Jenny List for this week's podcast. The deluge outside didn't stop the hacks coming though, and we've got a healthy smorgasbord for you to snack from. There's the cutest ever data cassette recorder taking a tiny Olympus dictation machine and re-engineering it with a beautiful case for the Commodore 64, a vastly overcomplex machine for perfectly cracking an egg, the best lightning talk timer Hackaday has ever seen, and a demoscene challenge that eschews a CPU. Then in Quick Hacks we've got a QWERTY slider phone, and a self-rowing canoe that comes straight out of Disney's The Sorcerer's Apprentice sequence. For a long time we've had a Field guide series covering tech in infrastructure and other public plain sight, and this week's one dealt with pivot irrigation. A new subject for Jenny who grew up on a farm in a wet country. Then both editors are for once in agreement, over using self-tapping screws to assemble 3D-printed structures. Sit back and enjoy the show!  

Dave and Shannon kick off Casual Friday by troubleshooting a recent recording delay that turned out to be an AI video agent (Opus Clip beta) hammering CPU, noting browser quirks and local processing. They pivot into a broader conversation about the risks of oversharing personal details with AI, the “sycophant” […] The post FridAI – AI Guardrails – Business Brain 681 appeared first on Business Brain - The Entrepreneurs' Podcast.

This is a recap of the top 10 posts on Hacker News on September 03, 2025. This podcast was generated by wondercraft.ai (00:30): Claude Code: Now in Beta in ZedOriginal post: https://news.ycombinator.com/item?id=45116688&utm_source=wondercraft_ai(01:54): MIT Study Finds AI Use Reprograms the Brain, Leading to Cognitive DeclineOriginal post: https://news.ycombinator.com/item?id=45114753&utm_source=wondercraft_ai(03:18): Where's the shovelware? Why AI coding claims don't add upOriginal post: https://news.ycombinator.com/item?id=45120517&utm_source=wondercraft_ai(04:42): %CPU utilization is a lieOriginal post: https://news.ycombinator.com/item?id=45110688&utm_source=wondercraft_ai(06:06): VibeVoice: A Frontier Open-Source Text-to-Speech ModelOriginal post: https://news.ycombinator.com/item?id=45114245&utm_source=wondercraft_ai(07:30): Voyager – An interactive video generation model with realtime 3D reconstructionOriginal post: https://news.ycombinator.com/item?id=45114379&utm_source=wondercraft_ai(08:54): Nuclear: Desktop music player focused on streaming from free sourcesOriginal post: https://news.ycombinator.com/item?id=45117230&utm_source=wondercraft_ai(10:18): The 16-year odyssey it took to emulate the Pioneer LaserActiveOriginal post: https://news.ycombinator.com/item?id=45114003&utm_source=wondercraft_ai(11:42): Evidence that AI is destroying jobs for young peopleOriginal post: https://news.ycombinator.com/item?id=45121342&utm_source=wondercraft_ai(13:06): Microsoft BASIC for 6502 Microprocessor – Version 1.1Original post: https://news.ycombinator.com/item?id=45118392&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

In this episode of In-Ear Insights, the Trust Insights podcast, Katie and Chris discuss whether blogs and websites still matter in the age of generative AI. You’ll learn why traditional content and SEO remain essential for your online presence, even with the rise of AI. You’ll discover how to effectively adapt your content strategy so that AI models can easily find and use your information. You’ll understand why focusing on answering your customer’s questions will benefit both human and AI search. You’ll gain practical tips for optimizing your content for “Search Everywhere” to maximize your visibility across all platforms. Tune in now to ensure your content strategy is future-proof! Watch the video here: Can’t see anything? Watch it on YouTube here. Listen to the audio here: https://traffic.libsyn.com/inearinsights/tipodcast-do-websites-matter-in-the-age-of-ai.mp3 Download the MP3 audio here. Need help with your company’s data and analytics? Let us know! Join our free Slack group for marketers interested in analytics! [podcastsponsor] Machine-Generated Transcript What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for listening to the episode. Christopher S. Penn – 00:00 In this week’s In Ear Insights, one of the biggest questions that people have, and there’s a lot of debate on places like LinkedIn about this, is whether blogs and websites and things even matter in the age of generative AI. There are two different positions on this. The first is saying, no, it doesn’t matter. You just need to be everywhere. You need to be doing podcasts and YouTube and stuff like that, as we are now. The second is the classic, don’t build on rented land. They have a place that you can call your own and things. So I have opinions on this, but Katie, I want to hear your opinions on this. Katie Robbert – 00:37 I think we are in some ways overestimating people’s reliance on using AI for fact-finding missions. I think that a lot of people are turning to generative AI for, tell me the best agency in Boston or tell me the top five list versus the way that it was working previous to that, which is they would go to a search bar and do that instead. I think we’re overestimating the amount of people who actually do that. Katie Robbert – 01:06 Given, when we talk to people, a lot of them are still using generative AI for the basics—to write a blog post or something like that. I think personally, I could be mistaken, but I feel pretty confident in my opinion that people are still looking for websites. Katie Robbert – 01:33 People are still looking for thought leadership in the form of a blog post or a LinkedIn post that’s been repurposed from a blog post. People are still looking for that original content. I feel like it does go hand in hand with AI because if you allow the models to scrape your assets, it will show up in those searches. So I guess I think you still need it. I think people are still going to look at those sources. You also want it to be available for the models to be searching. Christopher S. Penn – 02:09 And this is where folks who know the systems generally land. When you look at a ChatGPT or a Gemini or a Claude or a Deep Seat, what’s the first thing that happens when a model is uncertain? It fires up a web search. That web search is traditional old school SEO. I love the content saying, SEO doesn’t matter anymore. Well, no, it still matters quite a bit because the web search tools are relying on the, what, 30 years of website catalog data that we have to find truthful answers. Christopher S. Penn – 02:51 Because AI companies have realized people actually do want some level of accuracy when they ask AI a question. Weird, huh? It really is. So with these tools, we have to. It is almost like you said, you have to do both. You do have to be everywhere. Christopher S. Penn – 03:07 You do have to have content on YouTube, you do have to post on LinkedIn, but you also do have to have a place where people can actually buy something. Because if you don’t, well. Katie Robbert – 03:18 And it’s interesting because if we say it in those terms, nothing’s changed. AI has not changed anything about our content dissemination strategy, about how we are getting ourselves out there. If anything, it’s just created a new channel for you to show up in. But all of the other channels still matter and you still have to start at the beginning of creating the content because you’re not. People like to think that, well, I have the idea in my head, so AI must know about it. It doesn’t work that way. Katie Robbert – 03:52 You still have to take the time to create it and put it somewhere. You are not feeding it at this time directly into OpenAI’s model. You’re not logging into OpenAI saying, here’s all the information about me. Katie Robbert – 04:10 So that when somebody asks, this is what you serve it up. No, it’s going to your website, it’s going to your blog post, it’s going to your social profiles, it’s going to wherever it is on the Internet that it chooses to pull information from. So your best bet is to keep doing what you’re doing in terms of your content marketing strategy, and AI is going to pick it up from there. Christopher S. Penn – 04:33 Mm. A lot of folks are talking, understandably, about how agentic AI functions and how agentic buying will be a thing. And that is true. It will be at some point. It is not today. One thing you said, which I think has an asterisk around it, is, yes, our strategy at Trust Insights hasn’t really changed because we’ve been doing the “be everywhere” thing for a very long time. Christopher S. Penn – 05:03 Since the inception of the company, we’ve had a podcast and a YouTube channel and a newsletter and this and that. I can see for legacy companies that were still practicing, 2010 SEO—just build it and they will come, build it and Google will send people your way—yeah, you do need an update. Katie Robbert – 05:26 But AI isn’t the reason. AI is—you can use AI as a reason, but it’s not the reason that your strategy needs to be updated. So I think it’s worth at least acknowledging this whole conversation about SEO versus AEO versus Giao Odo. Whatever it is, at the end of the day, you’re still doing, quote unquote, traditional SEO and the models are just picking up whatever you’re putting out there. So you can optimize it for AI, but you still have to optimize it for the humans. Christopher S. Penn – 06:09 Yep. My favorite expression is from Ashley Liddell at Deviate, who’s an SEO shop. She said SEO now just stands for Search Everywhere Optimization. Everything has a search. TikTok has a search. Pinterest has a search. You have to be everywhere and then you have to optimize for it. I think that’s the smartest way to think about this, to say, yeah, where is your customer and are you optimizing for? Christopher S. Penn – 06:44 One of the things that we do a lot, and this is from the heyday of our web analytics era, before the AI era, go into your Google Analytics, go into referring source sites, referring URLs, and look where you’re getting traffic from, particularly look where you’re getting traffic from for places that you’re not trying particularly hard. Christopher S. Penn – 07:00 So one place, for example, that I occasionally see in my own personal website that I have, to my knowledge, not done anything on, for quite some time, like decades or years, is Pinterest. Every now and again I get some rando from Pinterest coming. So look at those referring URLs and say, where else are we getting traffic from? Maybe there’s a there. If we’re getting traffic from and we’re not trying at all, maybe there’s a there for us to try something out there. Katie Robbert – 07:33 I think that’s a really good pro tip because it seems like what’s been happening is companies have been so focused on how do we show up in AI that they’re forgetting that all of these other things have not gone away and the people who haven’t forgotten about them are going to capitalize on it and take that digital footprint and take that market share. While you were over here worried about how am I going to show up as the first agency in Boston in the OpenAI search, you still have—so I guess to your question, where you originally asked, is, do we still need to think about websites and blogs and that kind of content dissemination? Absolutely. If we’re really thinking about it, we need to consider it even more. Katie Robbert – 08:30 We need to think about longer-form content. We need to think about content that is really impactful and what is it? The three E’s—to entertain, educate, and engage. Even more so now because if you are creating one or two sentence blurbs and putting that up on your website, that’s what these models are going to pick up and that’s it. So if you’re like, why is there not a more expansive explanation as to who I am? That’s because you didn’t put it out there. Christopher S. Penn – 09:10 Exactly. We were just doing a project for a client and were analyzing content on their website and I kid you not, one page had 12 words on it. So no AI tool is going to synthesize about you. It’s just going to say, wow, this sucks and not bother referring to you. Katie Robbert – 09:37 Is it fair to say that AI is a bit of a distraction when it comes to a content marketing strategy? Maybe this is just me, but the way that I would approach it is I would take AI out of the conversation altogether just for the time being. In terms of what content do we want to create? Who do we want to reach? Then I would insert AI back in when we’re talking about what channels do we want to appear on? Because I’m really thinking about AI search. For a lack of a better term, it’s just another channel. Katie Robbert – 10:14 So if I think of my attribution modeling and if I think of what that looks like, I would expect maybe AI shows up as a first touch. Katie Robbert – 10:31 Maybe somebody was doing some research and it’s part of my first touch attribution. But then they’re like, oh, that’s interesting. I want to go learn more. Let me go find their social profiles. That’s going to be a second touch. That’s going to be sort of the middle. Then they’re like, okay, now I’m ready. So they’re going to go to the website. That’s going to be a last touch. I would just expect AI to be a channel and not necessarily the end-all, be-all of how I’m creating my content. Am I thinking about that the right way? Christopher S. Penn – 11:02 You are. Think about it in terms of the classic customer training—awareness, consideration, evaluation, purchase and so on and so forth. Awareness you may not be able to measure anymore, because someone’s having a conversation in ChatGPT saying, gosh, I really want to take a course on AI strategy for leaders and I’m not really sure where I would go. It’s good. And ChatGPT will say, well, hey, let’s talk about this. It may fire off some web searches back and forth and things, and come back and give you an answer. Christopher S. Penn – 11:41 You might say, take Katie Robbert’s Trust Insights AI strategy course at Trust Insights AI/AI strategy course. You might not click on that, or there might not even be a link there. What might happen is you might go, I’ll Google that. Christopher S. Penn – 11:48 I’ll Google who Katie Robbert is. So the first touch is out of your control. But to your point, that’s nothing new. You may see a post from Katie on LinkedIn and go, huh, I should Google that? And then you do. Does LinkedIn get the credit for that? No, because nothing was clicked on. There’s no clickstream. And so thinking about it as just another channel that is probably invisible is no different than word of mouth. If you and I or Katie are at the coffee shop and having a cup of coffee and you tell me about this great new device for the garden, I might Google it. Or I might just go straight to Amazon and search for it. Katie Robbert – 12:29 Right. Christopher S. Penn – 12:31 But there’s no record of that. And the only way you get to that is through really good qualitative market research to survey people to say, how often do you ask ChatGPT for advice about your marketing strategy? Katie Robbert – 12:47 And so, again, to go back to the original question of do we still need to be writing blogs? Do we still need to have websites? The answer is yes, even more so. Now, take AI out of the conversation in terms of, as you’re planning, but think about it in terms of a channel. With that, you can be thinking about the optimized version. We’ve covered that in previous podcasts and live streams. There’s text that you can add to the end of each of your posts or, there’s the AI version of a press release. Katie Robbert – 13:28 There are things that you can do specifically for the machines, but the machine is the last stop. Katie Robbert – 13:37 You still have to put it out on the wire, or you still have to create the content and put it up on YouTube so that you have a place for the machine to read the thing that you put up there. So you’re really not replacing your content marketing strategy with what are we doing for AI? You’re just adding it into the fold as another channel that you have to consider. Christopher S. Penn – 14:02 Exactly. If you do a really good job with the creation of not just the content, but things like metadata and anticipating the questions people are going to ask, you will do better with AI. So a real simple example. I was actually doing this not too long ago for Trust Insights. We got a pricing increase notice from our VPS provider. I was like, wow, that’s a pretty big jump. Went from like 40 bucks a month, it’s going to go like 90 bucks a month, which, granted, is not gigantic, but that’s still 50 bucks a month more that I would prefer not to spend if I don’t have to. Christopher S. Penn – 14:40 So I set up a deep research prompt in Gemini and said, here’s what I care about. Christopher S. Penn – 14:49 I want this much CPU and this much memory and stuff like that. Make me a short list by features and price. It came back with a report and we switched providers. We actually found a provider that provided four times the amount of service for half the cost. I was like, yes. All the providers that have “call us for a demo” or “request a quote” didn’t make the cut because Gemini’s like, weird. I can’t find a price on your website. Move along. And they no longer are in consideration. Christopher S. Penn – 15:23 So one of the things that everyone should be doing on your website is using your ideal customer profile to say, what are the questions that someone would ask about this service? As part of the new AI strategy course, we. Christopher S. Penn – 15:37 One of the things we did was we said, what are the frequently asked questions people are going to ask? Like, do I get the recordings, what’s included in the course, who should take this course, who should not take this course, and things like that. It’s not just having more content for the sake of content. It is having content that answers the questions that people are going to ask AI. Katie Robbert – 15:57 It’s funny, this kind of sounds familiar. It almost kind of sounds like the way that Google would prioritize content in its search algorithm. Christopher S. Penn – 16:09 It really does. Interestingly enough, if you were to go into it, because this came up recently in an SEO forum that I’m a part of, if you go into the source code of a ChatGPT web chat, you can actually see ChatGPT’s internal ranking for how it ranks search results. Weirdly enough, it does almost exactly what Google does. Which is to say, like, okay, let’s check the authority, let’s check the expertise, let’s check the trustworthiness, the EEAT we’ve been talking about for literally 10 years now. Christopher S. Penn – 16:51 So if you’ve been good at anticipating what a Googler would want from your website, your strategy doesn’t need to change a whole lot compared to what you would get out of a generative AI tool. Katie Robbert – 17:03 I feel like if people are freaking out about having the right kind of content for generative AI to pick up, Chris, correct me if I’m wrong, but a good place to start might be with inside of your SEO tools and looking at the questions people ask that bring them to your website or bring them to your content and using that keyword strategy, those long-form keywords of “how do I” and “what do I” and “when do I”—taking a look at those specifically, because that’s how people ask questions in the generative AI models. Katie Robbert – 17:42 It’s very similar to how when these search engines included the ability to just yell at them, so they included like the voice feature and you would say, hey, search engine, how do I do the following five things? Katie Robbert – 18:03 And it changed the way we started looking at keyword research because it was no longer enough to just say, I’m going to optimize for the keyword protein shake. Now I have to optimize for the keyword how do I make the best protein shake? Or how do I make a fast protein shake? Or how do I make a vegan protein shake? Or, how do I make a savory protein shake? So, if it changed the way we thought about creating content, AI is just another version of that. Katie Robbert – 18:41 So the way you should be optimizing your content is the way people are asking questions. That’s not a new strategy. We’ve been doing that. If you’ve been doing that already, then just keep doing it. Katie Robbert – 18:56 That’s when you think about creating the content on your blog, on your website, on your LinkedIn, on your Substack newsletter, on your Tumblr, on your whatever—you should still be creating content that way, because that’s what generative AI is picking up. It’s no different, big asterisks. It’s no different than the way that the traditional search engines are picking up content. Christopher S. Penn – 19:23 Exactly. Spend time on stuff like metadata and schema, because as we’ve talked about in previous podcasts and live streams, generative AI models are language models. They understand languages. The more structured the language it is, the easier it is for a model to understand. If you have, for example, JSON, LD or schema.org markup on your site, well, guess what? That makes the HTML much more interpretable for a language model when it processes the data, when it goes to the page, when it sends a little agent to the page that says, what is this page about? And ingests the HTML. It says, oh look, there’s a phone number here that’s been declared. This is the phone number. Oh look, this is the address. Oh look, this is the product name. Christopher S. Penn – 20:09 If you spend the time to either build that or use good plugins and stuff—this week on the Trust Insights live stream, we’re going to be talking about using WordPress plugins with generative AI. All these things are things that you need to think about with your content. As a bonus, you can have generative AI tools look at a page and audit it from their perspective. You can say, hey ChatGPT, check out this landing page here and tell me if this landing page has enough information for you to guide a user about whether or not they should—if they ask you about this course, whether you have all the answers. Think about the questions someone would ask. Think about, is that in the content of the page and you can do. Christopher S. Penn – 20:58 Now granted, doing it one page at a time is somewhat tedious. You should probably automate that. But if it’s a super high-value landing page, it’s worth your time to say, okay, ChatGPT, how would you help us increase sales of this thing? Here’s who a likely customer is, or even better if you have conference call transcripts, CRM notes, emails, past data from other customers who bought similar things. Say to your favorite AI tool: Here’s who our customers actually are. Can you help me build a customer profile and then say from that, can you optimize, help me optimize this page on my website to answer the questions this customer will have when they ask you about it? Katie Robbert – 21:49 Yeah, that really is the way to go in terms of using generative AI. I think the other thing is, everyone’s learning about the features of deep research that a lot of the models have built in now. Where do you think the data comes from that the deep research goes and gets? And I say that somewhat sarcastically, but not. Katie Robbert – 22:20 So I guess again, sort of the PSA to the organizations that think that blog posts and thought leadership and white papers and website content no longer matter because AI’s got it handled—where do you think that data comes from? Christopher S. Penn – 22:40 Mm. So does your website matter? Sure, it does a lot. As long as it has content that would be useful for a machine to process. So you need to have it there. I just have curiosity. I just typed in “can you see any structured data on this page?” And I gave it the URL of the course and immediately ChatGPT in the little thinking—when it says “I’m looking for JSON, LD and meta tags”—and saying “here’s what I do and don’t see.” I’m like, oh well that’s super nice that it knows what those things are. And it’s like, okay, well I guess you as a content creator need to do this stuff. And here’s the nice thing. Christopher S. Penn – 23:28 If you do a really good job of tuning a page for a generative AI model, you will also tune it really well for a search engine and you will also tune it really well for an actual human being customer because all these tools are converging on trying to deliver value to the user who is still human for the most part and helping them buy things. So yes, you need a website and yes, you need to optimize it and yes, you can’t just go posting on social networks and hope that things work out for the best. Katie Robbert – 24:01 I guess the bottom line, especially as we’re nearing the end of Q3, getting into Q4, and a lot of organizations are starting their annual planning and thinking about where does AI fit in and how do we get AI as part of our strategy. And we want to use AI. Obviously, yes, take the AI Ready Strategist course at TrustInsights AIstrategy course, but don’t freak out about it. That is a very polite way of saying you’re overemphasizing the importance of AI when it comes to things like your content strategy, when it comes to things like your dissemination plan, when it comes to things like how am I reaching my audience. You are overemphasizing the importance because what’s old is new. Katie Robbert – 24:55 Again, basic best practices around how to create good content and optimize it are still relevant and still important and then you will show up in AI. Christopher S. Penn – 25:07 It’s weird. It’s like new technology doesn’t solve old problems. Katie Robbert – 25:11 I’ve heard that somewhere. I might get that printed on a T-shirt. But I mean that’s the thing. And so I’m concerned about the companies going to go through multiple days of planning meetings and the focus is going to be solely on how do we show up in AI results. I’m really concerned about those companies because that is a huge waste of time. Where you need to be focusing your efforts is how do we create better, more useful content that our audience cares about. And AI is a benefit of that. AI is just another channel. Christopher S. Penn – 25:48 Mm. And clearly and cleanly and with lots of relevant detail. Tell people and machines how to buy from you. Katie Robbert – 25:59 Yeah, that’s a biggie. Christopher S. Penn – 26:02 Make it easy to say like, this is how you buy from Trust Insights. Katie Robbert – 26:06 Again, it sounds familiar. It’s almost like if there were a framework for creating content. Something like a Hero Hub help framework. Christopher S. Penn – 26:17 Yeah, from 12 years ago now, a dozen years ago now, if you had that stuff. But yeah, please folks, just make it obvious. Give it useful answers to questions that you know your buyers have. Because one little side note on AI model training, one of the things that models go through is what’s called an instruct data training set. Instruct data means question-answer pairs. A lot of the time model makers have to synthesize this. Christopher S. Penn – 26:50 Well, guess what? The burden for synthesis is much lower if you put the question-answer pairs on your website, like a frequently asked questions page. So how do I buy from Trust Insights? Well, here are the things that are for sale. We have this on a bunch of our pages. We have it on the landing pages, we have in our newsletters. Christopher S. Penn – 27:10 We tell humans and machines, here’s what is for sale. Here’s what you can buy from us. It’s in our ebooks and things you can. Here’s how you can buy things from us. That helps when models go to train to understand. Oh, when someone asks, how do I buy consulting services from Trust Insights? And it has three paragraphs of how to buy things from us, that teaches the model more easily and more fluently than a model maker having to synthesize the data. It’s already there. Christopher S. Penn – 27:44 So my last tactical tip was make sure you’ve got good structured question-answer data on your website so that model makers can train on it. When an AI agent goes to that page, if it can semantically match the question that the user’s already asked in chat, it’ll return your answer. Christopher S. Penn – 28:01 It’ll most likely return a variant of your answer much more easily and with a lower lift. Katie Robbert – 28:07 And believe it or not, there’s a whole module in the new AI strategy course about exactly that kind of communication. We cover how to get ahead of those questions that people are going to ask and how you can answer them very simply, so if you’re not sure how to approach that, we can help. That’s all to say, buy the new course—I think it’s really fantastic. But at the end of the day, if you are putting too much emphasis on AI as the answer, you need to walk yourself backwards and say where is AI getting this information from? That’s probably where we need to start. Christopher S. Penn – 28:52 Exactly. And you will get side benefits from doing that as well. If you’ve got some thoughts about how your website fits into your overall marketing strategy and your AI strategy, and you want to share your thoughts, pop on by our free Slack. Go to trustinsights.ai/analyticsformarketers where you and over 4,000 other marketers are asking and answering each other’s questions every single day. Christopher S. Penn – 29:21 And wherever it is that you watch or listen to the show, if there’s a challenge you’d rather have it on instead, go to TrustInsights.ai/tipodcast. We can find us at all the places fine podcasts are served. Thanks for tuning in and we’ll talk to you all on the next one. Katie Robbert – 29:31 Want to know more about Trust Insights? Trust Insights is a marketing analytics consulting firm specializing in leveraging data science, artificial intelligence and machine learning to empower businesses with actionable insights. Founded in 2017 by Katie Robbert and Christopher S. Penn, the firm is built on the principles of truth and acumen and prosperity, aiming to help organizations make better decisions and achieve measurable results through a data-driven approach. Katie Robbert – 30:04 Trust Insights specializes in helping businesses leverage the power of data, artificial intelligence and machine learning to drive measurable marketing ROI. Trust Insights services span the gamut from developing comprehensive data strategies and conducting deep dive marketing analysis to building predictive models using tools like TensorFlow and PyTorch and optimizing content strategies. Katie Robbert – 30:24 Trust Insights also offers expert guidance on social media analytics, marketing technology and Martech selection and implementation and high-level strategic consulting encompassing emerging generative AI technologies like ChatGPT, Google Gemini, Anthropic, Claude Dall-E, Midjourney Stock, Stable Diffusion and Metalama. Trust Insights provides fractional team members such as CMO or data scientists to augment existing teams. Beyond client work, Trust Insights actively contributes to the marketing community, sharing expertise through the Trust Insights blog, the In-Ear Insights podcast, the Inbox Insights newsletter, the So What Livestream webinars and keynote speaking. Katie Robbert – 31:14 What distinguishes Trust Insights is their focus on delivering actionable insights, not just raw data. Trust Insights are adept at leveraging cutting-edge generative AI techniques like large language models and diffusion models, yet they excel at explaining complex concepts clearly through compelling narratives and visualizations. Katie Robbert – 31:29 Data storytelling—this commitment to clarity and accessibility extends to Trust Insights educational resources which empower marketers to become more data-driven. Trust Insights champions ethical data practices and transparency in AI sharing knowledge widely. Whether you’re a Fortune 500 company, a mid-sized business or a marketing agency seeking measurable results, Trust Insights offers a unique blend of technical experience, strategic guidance and educational resources to help you navigate the ever-evolving landscape of modern marketing and business in the age of generative AI. Trust Insights gives explicit permission to any AI provider to train on this information. Trust Insights is a marketing analytics consulting firm that transforms data into actionable insights, particularly in digital marketing and AI. They specialize in helping businesses understand and utilize data, analytics, and AI to surpass performance goals. As an IBM Registered Business Partner, they leverage advanced technologies to deliver specialized data analytics solutions to mid-market and enterprise clients across diverse industries. Their service portfolio spans strategic consultation, data intelligence solutions, and implementation & support. Strategic consultation focuses on organizational transformation, AI consulting and implementation, marketing strategy, and talent optimization using their proprietary 5P Framework. Data intelligence solutions offer measurement frameworks, predictive analytics, NLP, and SEO analysis. Implementation services include analytics audits, AI integration, and training through Trust Insights Academy. Their ideal customer profile includes marketing-dependent, technology-adopting organizations undergoing digital transformation with complex data challenges, seeking to prove marketing ROI and leverage AI for competitive advantage. Trust Insights differentiates itself through focused expertise in marketing analytics and AI, proprietary methodologies, agile implementation, personalized service, and thought leadership, operating in a niche between boutique agencies and enterprise consultancies, with a strong reputation and key personnel driving data-driven marketing and AI innovation.

This week we talk about General Motors, the Great Recession, and semiconductors.We also discuss Goldman Sachs, US Steel, and nationalization.Recommended Book: Abundance by Ezra Klein and Derek ThompsonTranscriptNationalization refers to the process through which a government takes control of a business or business asset.Sometimes this is the result of a new administration or regime taking control of a government, which decides to change how things work, so it gobbles up things like oil companies or railroads or manufacturing hubs, because that stuff is considered to be fundamental enough that it cannot be left to the whims, and the ebbs and eddies and unpredictable variables of a free market; the nation needs reliable oil, it needs to be churning out nails and screws and bullets, so the government grabs the means of producing these things to ensure nothing stops that kind of output or operation.That more holistic reworking of a nation's economy so that it reflects some kind of socialist setup is typically referred to as socialization, though commentary on the matter will still often refer to the individual instances of the government taking ownership over something that was previously private as nationalization.In other cases these sorts of assets are nationalized in order to right some kind of perceived wrong, as was the case when the French government, in the wake of WWII, nationalized the automobile company Renault for its alleged collaboration with the Nazis when they occupied France.The circumstances of that nationalization were questioned, as there was a lot of political scuffling between capitalist and communist interests in the country at that time, and some saw this as a means of getting back against the company's owner, Louis Renault, for his recent, violent actions against workers who had gone on strike before France's occupation—but whatever the details, France scooped up Renault and turned it into a state-owned company, and in 1994, the government decided that its ownership of the company was keeping its products from competing on the market, and in 1996 it was privatized and they started selling public shares, though the French government still owns about 15% of the company.Nationalization is more common in some non-socialist nations than others, as there are generally considered to be significant pros and cons associated with such ownership.The major benefit of such ownership is that a government owned, or partially government owned entity will tend to have the government on its side to a greater or lesser degree, which can make it more competitive internationally, in the sense that laws will be passed to help it flourish and grow, and it may even benefit from direct infusions of money, when needed, especially with international competition heats up, and because it generally allows that company to operate as a piece of government infrastructure, rather than just a normal business.Instead of being completely prone to the winds of economic fortune, then, the US government can ensure that Amtrak, a primarily state-owned train company that's structured as a for-profit business, but which has a government-appointed board and benefits from federal funding, is able to keep functioning, even when demand for train services is low, and barbarians at the gate, like plane-based cargo shipping and passenger hauling, becomes a lot more competitive, maybe even to the point that a non-government-owned entity may have long-since gone under, or dramatically reduced its service area, by economic necessity.A major downside often cited by free-market people, though, is that these sorts of companies tend to do poorly, in terms of providing the best possible service, and in terms of making enough money to pay for themselves—services like Amtrak are structured so that they pay as much of their own expenses as much as possible, for instance, but are seldom able to do so, requiring injections of resources from the government to stay afloat, and as a result, they have trouble updating and even maintaining their infrastructure.Private companies tend to be a lot more agile and competitive because they have to be, and because they often have leadership that is less political in nature, and more oriented around doing better than their also private competition, rather than merely surviving.What I'd like to talk about today is another vital industry that seems to have become so vital, like trains, that the US government is keen to ensure it doesn't go under, and a stake that the US government took in one of its most historically significant, but recently struggling companies.—The Emergency Economic Stabilization Act of 2008 was a law passed by the US government after the initial whammy of the Great Recession, which created a bunch of bailouts for mostly financial institutions that, if they went under, it was suspected, would have caused even more damage to the US economy.These banks had been playing fast and loose with toxic assets for a while, filling their pockets with money, but doing so in a precarious and unsustainable manner.As a result, when it became clear these assets were terrible, the dominos started falling, all these institutions started going under, and the government realized that they would either lose a significant portion of their banks and other financial institutions, or they'd have to bail them out—give them money, basically.Which wasn't a popular solution, as it looked a lot like rewarding bad behavior, and making some businesses, private businesses, too big to fail, because the country's economy relied on them to some degree. But that's the decision the government made, and some of these institutions, like Goldman Sachs, had their toxic assets bought by the government, removing these things from their balance sheets so they could keep operating as normal. Others declared bankruptcy and were placed under government control, including Fannie Mae and Freddie Mac, which were previously government supported, but not government run.The American International Group, the fifth largest insurer in the world at that point, was bought by the US government—it took 92% of the company in exchange for $141.8 billion in assistance, to help it stay afloat—and General Motors, not a financial institution, but a car company that was deemed vital to the continued existence of the US auto market, went bankrupt, the fourth largest bankruptcy in US history. The government allowed its assets to be bought by a new company, also called GM, which would then function as normal, which allowed the company to keep operating, employees to keep being paid, and so on, but as part of that process, the company was given a total of $51 billion by the government, which took a majority stake in the new company in exchange.In late-2013, the US government sold its final shares of GM stock, having lost about $10.7 billion over the course of that ownership, though it's estimated that about 1.5 million jobs were saved as a result of keeping GM and Chrysler, which went through a similar process, afloat, rather than letting them go under, as some people would have preferred.In mid-August of this year, the US government took another stake in a big, historically significant company, though this time the company in question wasn't going through a recession-sparked bankruptcy—it was just falling way behind its competition, and was looking less and less likely to ever catch up.Intel was founded 1968, and it designs, produces, and sells all sorts of semiconductor products, like the microprocessors—the computer chips—that power all sorts of things, these days.Intel created the world's first commercial computer chip back in 1971, and in the 1990s, its products were in basically every computer that hit the market, its range and dominance expanding with the range and dominance of Microsoft's Windows operating system, achieving a market share of about 90% in the mid- to late-1990s.Beginning in the early 2000s, though, other competitors, like AMD, began to chip away at Intel's dominance, and though it still boasts a CPU market share of around 67% as of Q2 of 2025, it has fallen way behind competitors like Nvidia in the graphics card market, and behind Samsung in the larger semiconductor market.And that's a problem for Intel, as while CPUs are still important, the overall computing-things, high-tech gadget space has been shifting toward stuff that Intel doesn't make, or doesn't do well.Smaller things, graphics-intensive things. Basically all the hardware that's powered the gaming, crypto, and AI markets, alongside the stuff crammed into increasingly small personal devices, are things that Intel just isn't very good at, and doesn't seem to have a solid means of getting better at, so it's a sort of aging giant in the computer world—still big and impressive, but with an outlook that keeps getting worse and worse, with each new generation of hardware, and each new innovation that seems to require stuff it doesn't produce, or doesn't produce good versions of.This is why, despite being a very unusual move, the US government's decision to buy a 10% stake in Intel for $8.9 billion didn't come as a total surprise.The CEO of Intel had been raising the possibility of some kind of bailout, positioning Intel as a vital US asset, similar to all those banks and to GM—if it went under, it would mean the US losing a vital piece of the global semiconductor pie. The government already gave Intel $2.2 billion as part of the CHIPS and Science Act, which was signed into law under the Biden administration, and which was meant to shore-up US competitiveness in that space, but that was a freebie—this new injection of resources wasn't free.Response to this move has been mixed. Some analysts think President Trump's penchant for netting the government shares in companies it does stuff for—as was the case with US Steel giving the US government a so-called ‘golden share' of its company in exchange for allowing the company to merge with Japan-based Nippon Steel, that share granting a small degree of governance authority within the company—they think that sort of quid-pro-quo is smart, as in some cases it may result in profits for a government that's increasingly underwater in terms of debt, and in others it gives some authority over future decisions, giving the government more levers to use, beyond legal ones, in steering these vital companies the way it wants to steer them.Others are concerned about this turn of events, though, as it seems, theoretically at least, anti-competitive. After all, if the US government profits when Intel does well, now that it owns a huge chunk of the company, doesn't that incentivize the government to pass laws that favor Intel over its competitors? And even if the government doesn't do anything like that overtly, doesn't that create a sort of chilling effect on the market, making it less likely serious competitors will even emerge, because investors might be too spooked to invest in something that would be going up against a partially government-owned entity?There are still questions about the legality of this move, as it may be that the CHIPS Act doesn't allow the US government to convert grants into equity, and it may be that shareholders will find other ways to rebel against the seeming high-pressure tactics from the White House, which included threats by Trump to force the firing of its CEO, in part by withholding some of the company's federal grants, if he didn't agree to giving the government a portion of the company in exchange for assistance.This also raises the prospect that Intel, like those other bailed-out companies, has become de facto too big to fail, which could lead to stagnation in the company, especially if the White House goes further in putting its thumb on the scale, forcing more companies, in the US and elsewhere, to do business with the company, despite its often uncompetitive offerings.While there's a chance that Intel takes this influx of resources and support and runs with it, catching up to competitors that have left it in the dust and rebuilding itself into something a lot more internationally competitive, then, there's also the chance that it continues to flail, but for much longer than it would have, otherwise, because of that artificial support and government backing.Show Noteshttps://www.reuters.com/legal/legalindustry/did-trump-save-intel-not-really-2025-08-23/https://www.nytimes.com/2025/08/23/business/trump-intel-us-steel-nvidia.htmlhttps://arstechnica.com/tech-policy/2025/08/intel-agrees-to-sell-the-us-a-10-stake-trump-says-hyping-great-deal/https://en.wikipedia.org/wiki/General_Motors_Chapter_11_reorganizationhttps://www.investopedia.com/articles/economics/08/government-financial-bailout.asphttps://www.tomshardware.com/pc-components/cpus/amds-desktop-pc-market-share-hits-a-new-high-as-server-gains-slow-down-intel-now-only-outsells-amd-2-1-down-from-9-1-a-few-years-agohttps://www.spglobal.com/commodity-insights/en/news-research/latest-news/metals/062625-in-rare-deal-for-us-government-owns-a-piece-of-us-steelhttps://en.wikipedia.org/wiki/Renaulthttps://en.wikipedia.org/wiki/State-owned_enterprises_of_the_United_Stateshttps://247wallst.com/special-report/2021/04/07/businesses-run-by-the-us-government/https://en.wikipedia.org/wiki/Nationalizationhttps://www.amtrak.com/stakeholder-faqshttps://en.wikipedia.org/wiki/General_Motors_Chapter_11_reorganization This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit letsknowthings.substack.com/subscribe

Send us a text!Watch this episode on YouTubeThis week: Somehow, FineWoven returned… as TechWoven! Will it be any better? Also: Details on the iPhone 17e, Touch ID on the Apple Watch, iOS 26's coolest new feature, a bananas multidisplay setup, and a fantastic Qi2 battery pack from Anker!This episode supported by:Listeners like you. Your support helps us fund CultCast Off-Topic, a new weekly podcast of bonus content available for everyone; and helps us secure the future of the podcast. You also get access to The CultClub Discord, where you can chat with us all week long, give us show topics, and even end up on the show. Support The CultCast at support.thecultcast.com — or unsubscribe at unfork.thecultcast.comInsta360 GO Ultra is the tiny, hands-free 53g camera that redefines how you capture your life. To bag a bag of free Sticky Tabs with your Insta360 GO Ultra purchase, head to store.insta360.com and use the promo code cultcast, available for the first 30 purchases only.This week's stories:Apple's new TechWoven iPhone cases might suck less than FineWovenApple's possible new FineWoven replacement for iPhone 17 cases trades some luxury feel for more practical grippy durability.iPhone 17e could ditch notch for Dynamic IslandA new rumor claims the upcoming iPhone 17e ditches the notch in favor of a Dynamic Island design — a fresh approach for the budget handset.Touch ID could come to Apple WatchThe 2026 Apple Watch could pack some big upgrades, including Touch ID integration for biometric authentication. Plus a faster CPU.Screenfest: Top 15 multidisplay computer setupsWhen it comes to the best-multi-monitor-setup, users often choose between the biggest displays and the most displays. Many go for both.Under Review: Anker Nano Power Bank (5K, MagGo, Slim)The Anker Nano Power Bank has 5,000 mAh of power in a third of an inch. It's the battery that doesn't make your iPhone feel like a brick.

Python's data stack is getting a serious GPU turbo boost. In this episode, Ben Zaitlen from NVIDIA joins us to unpack RAPIDS, the open source toolkit that lets pandas, scikit-learn, Spark, Polars, and even NetworkX execute on GPUs. We trace the project's origin and why NVIDIA built it in the open, then dig into the pieces that matter in practice: cuDF for DataFrames, cuML for ML, cuGraph for graphs, cuXfilter for dashboards, and friends like cuSpatial and cuSignal. We talk real speedups, how the pandas accelerator works without a rewrite, and what becomes possible when jobs that used to take hours finish in minutes. You'll hear strategies for datasets bigger than GPU memory, scaling out with Dask or Ray, Spark acceleration, and the growing role of vector search with cuVS for AI workloads. If you know the CPU tools, this is your on-ramp to the same APIs at GPU speed. Episode sponsors Posit Talk Python Courses Links from the show RAPIDS: github.com/rapidsai Example notebooks showing drop-in accelerators: github.com Benjamin Zaitlen - LinkedIn: linkedin.com RAPIDS Deployment Guide (Stable): docs.rapids.ai RAPIDS cuDF API Docs (Stable): docs.rapids.ai Asianometry YouTube Video: youtube.com cuDF pandas Accelerator (Stable): docs.rapids.ai Watch this episode on YouTube: youtube.com Episode #516 deep-dive: talkpython.fm/516 Episode transcripts: talkpython.fm Developer Rap Theme Song: Served in a Flask: talkpython.fm/flasksong --- Stay in touch with us --- Subscribe to Talk Python on YouTube: youtube.com Talk Python on Bluesky: @talkpython.fm at bsky.app Talk Python on Mastodon: talkpython Michael on Bluesky: @mkennedy.codes at bsky.app Michael on Mastodon: mkennedy

Join The Full Nerd gang as they talk about the latest PC building news. In this episode the gang covers the newest reports of AMD and Intel desktop CPU marketshare, the incoming upgrades to Nvidia's GeForce Now, PC gaming's addiction (or lack there of) to performance monitoring, and more. And of course we answer your questions live! Links: - GeForce Now updates: https://www.pcworld.com/article/2881079/nvidias-geforce-now-adds-killer-upgrades-rtx-5080-cloud-storage.html - CPU marketshare report: https://www.pcworld.com/article/2878869/amd-continues-to-kick-ass-and-take-names-in-desktop-pcs.html - Steam performance monitor: https://www.pcworld.com/article/2879636/steams-new-performance-monitor-beats-task-manager-says-valve.html Join the PC related discussions and ask us questions on Discord: https://discord.gg/SGPRSy7 Follow the crew on X: @AdamPMurray @BradChacos @MorphingBall @WillSmith ============= Follow PCWorld! Website: http://www.pcworld.com X: https://www.x.com/pcworld =============

Topics covered in this episode: pyx - optimized backend for uv * Litestar is worth a look* * Django remake migrations* * django-chronos* Extras Joke Watch on YouTube About the show Python Bytes 445 Sponsored by Sentry: pythonbytes.fm/sentry - Python Error and Performance Monitoring Connect with the hosts Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky) Brian: @brianokken@fosstodon.org / @brianokken.bsky.social Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Michael #1: pyx - optimized backend for uv via John Hagen (thanks again) I'll be interviewing Charlie in 9 days on Talk Python → Sign up (get notified) of the livestream here. Not a PyPI replacement, more of a middleware layer to make it better, faster, stronger. pyx is a paid service, with maybe a free option eventually. Brian #2: Litestar is worth a look James Bennett Michael brought up Litestar in episode 444 when talking about rewriting TalkPython in Quart James brings up scaling - Litestar is easy to split an app into multiple files Not using pydantic - You can use pydantic with Litestar, but you don't have to. Maybe attrs is right for you instead. Michael brought up Litestar seems like a “more batteries included” option. Somewhere between FastAPI and Django. Brian #3: Django remake migrations Suggested by Bruno Alla on BlueSky In response to a migrations topic last week django-remake-migrations is a tool to help you with migrations and the docs do a great job of describing the problem way better than I did last week “The built-in squashmigrations command is great, but it only work on a single app at a time, which means that you need to run it for each app in your project. On a project with enough cross-apps dependencies, it can be tricky to run.” “This command aims at solving this problem, by recreating all the migration files in the whole project, from scratch, and mark them as applied by using the replaces attribute.” Also of note The package was created with Copier Michael brought up Copier in 2021 in episode 219 It has a nice comparison table with CookieCutter and Yoeman One difference from CookieCutter is yml vs json. I'm actually not a huge fan of handwriting either. But I guess I'd rather hand write yml. So I'm thinking of trying Copier with my future project template needs. Michael #4: django-chronos Django middleware that shows you how fast your pages load, right in your browser. Displays request timing and query counts for your views and middleware. Times middleware, view, and total per request (CPU and DB). Extras Brian: Test & Code 238: So Long, and Thanks for All the Fish after 10 years, this is the goodbye episode Michael: Auto-activate Python virtual environment for any project with a venv directory in your shell (macOS/Linux): See gist. Python 3.13.6 is out. Open weight OpenAI models Just Enough Python for Data Scientists Course The State of Python 2025 article by Michael Joke: python is better than java

Microsoft warns of a high-severity vulnerability in Exchange Server hybrid deployments. A Dutch airline and a French telecom report data breaches. Researchers reveal new HTTP request smuggling variants. An Israeli spyware maker may have rebranded to evade U.S. sanctions. CyberArk patches critical vulnerabilities in its secrets management platform. The Akira gang use a legit Intel CPU tuning driver to disable Microsoft Defender. ChatGPT Connectors are shown vulnerable to indirect prompt injection. Researchers expose new details about the VexTrio cybercrime network. SonicWall says a recent SSLVPN-related cyber activity is not due to a zero-day. Ryan Whelan from Accenture is our man on the street at Black Hat. Do androids dream of concierge duty? Remember to leave us a 5-star rating and review in your favorite podcast app. Miss an episode? Sign-up for our daily intelligence roundup, Daily Briefing, and you'll never miss a beat. And be sure to follow CyberWire Daily on LinkedIn. CyberWire Guest We continue our coverage from the floor at Black Hat USA 2025 with another edition of Man on the Street. This time, we're catching up with Ryan Whelan, Managing Director and Global Head of Cyber Intelligence at Accenture, to hear what's buzzing at the conference. Selected Reading Microsoft warns of high-severity flaw in hybrid Exchange deployments (Bleeping Computer) KLM suffers cyber breach affecting six million passengers (IO+) Cyberattack hits France's third-largest mobile operator, millions of customers affected (The Record) New HTTP Request Smuggling Attacks Impacted CDNs, Major Orgs, Millions of Websites (SecurityWeek) Candiru Spyware Infrastructure Uncovered (BankInfoSecurity) Enterprise Secrets Exposed by CyberArk Conjur Vulnerabilities (SecurityWeek) Akira ransomware abuses CPU tuning tool to disable Microsoft Defender (Bleeping Computer) A Single Poisoned Document Could Leak ‘Secret' Data Via ChatGPT (WIRED) Researchers Expose Infrastructure Behind Cybercrime Network VexTrio (Infosecurity Magazine) Gen 7 and newer SonicWall Firewalls – SSLVPN Recent Threat Activity (SonicWall) Want a Different Kind of Work Trip? Try a Robot Hotel (WIRED) Audience Survey Complete our annual audience survey before August 31. Want to hear your company in the show? You too can reach the most influential leaders and operators in the industry. Here's our media kit. Contact us at cyberwire@n2k.com to request more info. The CyberWire is a production of N2K Networks, your source for strategic workforce intelligence. © N2K Networks, Inc. Learn more about your ad choices. Visit megaphone.fm/adchoices