English-language podcasts

Merge Conflict

541: .NET 11 Launch: Performance Gains, Union Types, and Runtime Changes

33 min

Listen through the publisher, then discuss the episode here or arrange an in-person Roundtable. Your city determines where to meet.

Roundtables are designed for groups of four, with a shared subject and room for everyone to speak. Come for discussion, with no dating expectation.

James and Frank dive into .NET 11's biggest announcements from .NET Conf 2026, exploring the performance optimizations that matter most to developers—from native AOT CLI tools shaving milliseconds off startup times to runtime async improvements that make your code faster without changes. They break down union types, MAUI's runtime consolidation, and why the team is obsessed with squeezing every millisecond for modern development workflows. Chapters 00:00 Welcome and Studio Setup Chat 01:13 .NET 11 Launch and .NET Conf 02:52 Building the .NET Conf Q&A Platform 09:17 Performance Optimizations and Native AOT 13:54 Runtime Async Preview Feature 18:33 Union Types and Type Safety 23:25 MCP Servers and AI Integration 25:40 MAUI Runtime Consolidation and Mobile 31:12 Feature Roundup and Community Engagement Links Announcing .NET 11 - .NET Blog (https://devblogs.microsoft.com/dotnet/announcing-dotnet-11/) Frank: Twitter (http://twitter.com/praeclarum), Blog (http://praeclarum.org/), GitHub (http://github.com/praeclarum) James: Twitter (http://twitter.com/jamesmontemagno), Blog (https://montemagno.com/), GitHub (http://github.com/jamesmontemagno) Merge Conflict: Twitter (http://twitter.com/mergeconflictfm), Facebook (https://www.facebook.com/mergeconflictfm), Website (http://mergeconflict.fm/), Chat on Discord (https://www.mergeconflict.fm/discord) Music : Amethyst Seer - Citrine by Adventureface (https://soundcloud.com/adventureface) ⭐⭐ Review Us (https://itunes.apple.com/us/podcast/merge-conflict/id1133064277?ls=1&mt=2) ⭐⭐ Machine transcription available on http://mergeconflict.fm (http://mergeconflict.fm/) Support Merge Conflict (https://www.patreon.com/mergeconflictfm) Links: Announcing .NET 11 - .NET Blog (https://devblogs.microsoft.com/dotnet/announcing-dotnet-11/)

Episode information is provided by the publisher. Listening takes place on the publisher’s service.

Listen at the source ↗

Featured places to meet in Palo Alto, CA

Explore these places and arrange a conversation through ThinkMatch.

City guide for Palo Alto, CA

More from Merge Conflict

Merge Conflict

540: Siri AI SDK: Finally Making App Integration Work

50 min

James and Frank dive into episode 540's lightning topics, exploring Apple's new Siri AI SDK that finally brings proper agentic app integration, Frank's smooth experience adding iPhone Duo support, and James's transformative use of Copilot Fusion for development. They also celebrate Tiny Clips as "real software," discuss bundling skills with NuGet packages, and break down the urgent .NET 8 & 9 end-of-life deadline before previewing an action-packed .NET Conf lineup. Chapters 00:00 Opening and Lightning Topics Format 02:06 Siri AI SDK and App Integration 14:18 iPhone Duo Development Challenges 25:01 Copilot Fusion and AI Tools 31:52 Tiny Clips: Building Real Software 36:55 NuGet Skills for Libraries 42:14 .NET Updates and Conference 48:32 Closing and Channel Info Frank: Twitter (http://twitter.com/praeclarum), Blog (http://praeclarum.org/), GitHub (http://github.com/praeclarum) James: Twitter (http://twitter.com/jamesmontemagno), Blog (https://montemagno.com/), GitHub (http://github.com/

Discuss this episode

Community Poll

A tradition can remain authentic while changing with the community that practices it.

Share your view, then see how readers voted. No sign-in required. This poll is shared across stories.

Do you agree or disagree?

Choose one answer

Common Quandary

A Common Quandary to discuss

Another conversation to explore, separate from this news story.

A pricey AI tutor can turn B students into A students. Should schools let them use it?

An effective AI tutor adapts to each student and dramatically improves performance, but its subscription is expensive. A public school cannot provide it to everyone and worries that allowing its use will deepen existing inequality.

Should access be limited when a beneficial tool cannot yet be shared fairly?

Explore this quandary