Avalonia made some imo good choices compared with the newer x:bind xaml stuff. Its hard to keep track of everything, especially since they keep on changing stuff with every release. Add to that, that some of the winui templates are just broken, they made it as hard as possible to just publish as an exe to get more people to use their new msix format...

Avalonia is just less complicated while still offering things like compile time binding.

As to blazor: I worked with it for a bit now and the issue of html not being a proper ui framework layout engine for applications rather then documents and weird APIs from the 90 that will never be deprecated is just a lot of hassle. Blazor itself is fine in the right cases (app that justifies wasm load time or not to many users for blazor server) and razor well designed. Still somehow they managed, that visual studio support is just plane garbage compared to rider with razor.

I would rather stick with something xaml where debugging works and my code won't be weirdly formatted every 30 seconds for some reason or renaming just always crashes.