Why do you let your developers use XAML?

Serious question.

If you employ or manage developers who use XAML to develop apps (with MAUI, WPF, WinUI, UWP, or anything else), those same developers will almost certainly tell you that:

XAML is verbose, complicated, and difficult to maintain. (And that's if they're being polite!)

The consequence of this is that the development and maintenance of that code is slower and, therefore, more expensive.

• Why is that acceptable?

• Have you asked those developers why they're using XAML?
• Or, what alternatives they've considered?
• Or, about ways to write/use XAML that address some of those issues?
• Or, if there are tools available (or could easily be created) that would help?

Then, if they've not already thought about these questions, ask yourself what other decisions they have made that are impacting their productivity and that of the project/business.

Using C# probably isn't the alternative you seek (although sometimes suggested) because it's not going to address the fact you already have loads of XAML.

Do you really have the time, resources, and test coverage to rewrite existing code rather than work on new products, features, bug fixes, etc.?

There are solutions, and I talked about many of them recently in a conference presentation that I summarized in(1) this(2) series(3) of(4) posts(5).

If you have projects written with XAML that you wish were easier to maintain, let's talk.

If you're about to start writing a new app and are going to use XAML, let me point you towards success.

If you're considering hiring someone to help write XAML (& C#), mentor those who are, or review what they're writing, I currently have space in my calendar.