The state (& future?) of XAML - A summary of a summary

Last week I gave a talk to a room full of .NET MAUI developers about "Rethinking UI Code".

The talks at the conference weren't recorded so I wrote up some of the key details for anyone not there but interested. 

That write-up became quite long, so here's the very short version (because I know you're busy):

• Everyone agrees that XAML has issues but loads of people still use it anyway.
• There are ways to make XAML much nicer to work with, but few realize this.
• Many of these improvements can be made by treating XAML like you would any other programming language.
• C# probably isn't the solution you want unless you want to rewrite everything you already have.
• I have lots of tools that can generate code and make XAML easier to work with.
• I've created a prototype of a language (I'm currently calling ENAMEL) that produces XAML and so sits on top of existing tools and toolchains. This language helps address many criticisms of working with XAML.
• I've done this as a way to encourage further discussion about what's possible and what the future might hold. (Not because I have answers. But because I have lots and lots of questions.) 

Now that you're intrigued, you can go and read the full version here or as a series on LinkedIn.