Adelaide .net User Group Podcast

Whether it be MAUI, WPF, WinUI, Xamarin.Forms, UWP, Uno Platform, Avalonia, or any other technology that defines UIs with XAML, there are some common complaints about working with XAML files that have been around as long as XAML has. It can be hard to write, understand, maintain and modify. But, it doesn't have to be this way. The solution isn't abandoning XAML entirely, adopting a new framework, or using a different pattern. The solution is treating XAML like a "real programming language." By comparing it with how we write and work with C# and other files we compile into our applications, let me show you what we've been doing wrong, how we can do things differently, how it makes things better, and give you strategies for improving existing codebases. Or, you can tell me why I'm wrong, and that it's still appropriate that the XAML files created today look like the ones created 15+ years ago.. Links: Matt's blog Matt on Twitter