Andy Gocke's guest appearances

Andy Gocke

no dogma podcast

OwlTail

SummaryAndy Gocke, lead of the native AOT and app model team at Microsoft talks about ahead-of-time compilation (AOT) in .NET.DetailsWho he is, what he does. Quick overview of ahead-of-time compilation (AOT); finding your code. Traditional compilation, interpreter vs compiler, translation from source to target languages. Operating systems, intermediate language (IL). There's always an interpreter. Just-in-time compilation (JIT); Java ran on multiple OSes, but .NET was Windows only; .NET ran on multiple architectures. Ready-to-run (R2R) and trimming. Tiered compilation, variable performance. R2R mixes precompiled and IL, native AOT only has precompiled. Trimming - getting rid of unneeded things, trouble with plugins and reflection; static analysis - don't ignore warnings. Why AOT was built, where it is a good fit. How much work it was; Core RT, low adoption, but good feedback. Good and bad use cases for AOT. For .NET 7 console apps and libraries, or if you don't get trim warnings; a single trim warning is too many. AOT and non-AOT OSS NuGet packages. .NET 8 support for ASP.NET. JIT and IL will not go away. AWS Lambda functions and AOT, exclusions, problems that might occur; trimmable all the way down. Getting started with AOT. Can't turn off trimming. Future of AOT.Support this podcastFull show notes@andygockeNative AOT deploymentAndy's de/serializer Serde-dnMore C# episodes

SummaryAndy Gocke, lead of the native AOT and app model team at Microsoft talks about ahead-of-time compilation (AOT) in .NET.DetailsWho he is, what he does. Quick overview of ahead-of-time compilation (AOT); finding your code. Traditional compilation, interpreter vs compiler, translation from source to target languages. Operating systems, intermediate language (IL). There's always an interpreter. Just-in-time compilation (JIT); Java ran on multiple OSes, but .NET was Windows only; .NET ran on multiple architectures. Ready-to-run (R2R) and trimming. Tiered compilation, variable performance. R2R mixes precompiled and IL, native AOT only has precompiled. Trimming - getting rid of unneeded things, trouble with plugins and reflection; static analysis - don't ignore warnings. Why AOT was built, where it is a good fit. How much work it was; Core RT, low adoption, but good feedback. Good and bad use cases for AOT. For .NET 7 console apps and libraries, or if you don't get trim warnings; a single trim warning is too many. AOT and non-AOT OSS NuGet packages. .NET 8 support for <a href="http://ASP.NET" rel="nofollow" target="_blank">ASP.NET</a>. JIT and IL will not go away. AWS Lambda functions and AOT, exclusions, problems that might occur; trimmable all the way down. Getting started with AOT. Can't turn off trimming. Future of AOT.<a href="https://www.buymeacoffee.com/l2ABIax" rel="nofollow" target="_blank">Support this podcast</a><a href="https://nodogmapodcast.bryanhogan.net/171-andy-gocke-net-ahead-of-time-compilation-part-1" rel="nofollow" target="_blank">Full show notes</a> <a href="https://www.twitter.com/andygocke" rel="nofollow" target="_blank">@andygocke</a> <a href="https://learn.microsoft.com/en-us/dotnet/core/deploying/native-aot/" rel="nofollow" target="_blank">Native AOT deployment</a> <a href="https://github.com/agocke/serde-dn" rel="nofollow" target="_blank">Andy's de/serializer Serde-dn</a> <a href="https://nodogmapodcast.bryanhogan.net/tag/c/" rel="nofollow" target="_blank">More C# episodes</a>