In my experience XAML can be a massive footgun if you don't know what you're doing. Sure, world-class geniuses are using it to build (still) the best IDE on the

In my experience XAML can be a massive footgun if you don't know what you're doing. Sure, world-class geniuses are using it to build (still) the best IDE on the planet, but on your everyday development team it can backfire. One of React's biggest selling points is that it has a sort of "pit of success" instead. Partly from the mandatory one-way binding, and partly because of the choice to allow integrating any kind of UI "thing" into the component model.