3 ms·
C# with hot reload. Issues with XAML: - verbose - static (not good fit for dynamic UIs) - templating is unnecessarily complex - contains code-like construc
by zigzag312 5y ago
C# with hot reload.
Issues with XAML:
- verbose
- static (not good fit for dynamic UIs)
- templating is unnecessarily complex
- contains code-like constructs (behaviors, convertors)
- being a separate language forces constant mental context switching when developing, which is bad for productivity. Tooling is more complex and breaks more often (like Intellisense issues)
The only good thing that XAML does is separates UI from the model, but you really don't need a separate language to do that.
What would you say are the benefits of XAML that warrant using another language for UI?
- jayd16 5y ago>What would you say are the benefits of XAML that warrant using another language for UI? I think the main reason is they wanted a declarative language along side their imperative language. You don't necessarily need to recompile anything to get a layout drawn in an editor with XAML.