I disagree. I haven't worked in XAML for a few years and I wouldn't recommend it on almost any application (unless a windows specific desktop). But the only reasons I don't recommend it is because it is windows specific.
Aside from that the true power of xaml is it allows you to change anything. For example, A radio button group, checkbox list, drop down, expandable list or searchable list could all derive from the same basic component AND same set of data. In html that would be like saying this (warning, lots of fake code below)
That is COOOL and it has been around since XAML was created. We've tried to get to the same place with jquery templates but they have always been hackish approaches to templating/styling
Aside from that the true power of xaml is it allows you to change anything. For example, A radio button group, checkbox list, drop down, expandable list or searchable list could all derive from the same basic component AND same set of data. In html that would be like saying this (warning, lots of fake code below)
<div class="dropDown" data="['frank','sam','larry']"/>
<div class="expanderBar" data="['frank','sam','larry']"/>
<div class="radioButton" data="['frank','sam','larry']"/>
<class id="radioButton"> <div style="border:1px solid black"> <loop value="data" var="item"> <input type="radio" name="user" checked="condition">${item} </loop> </div> </class>
...and so on
That is COOOL and it has been around since XAML was created. We've tried to get to the same place with jquery templates but they have always been hackish approaches to templating/styling