Additionally, you would think that after the flaming failure of project.json, where it was horrifically discovered that JSON does not support simple constructs such as comments that more efforts would be made to steer clear of it altogether (or again at least, offer an XML/Xaml/YAML/TOML -- or even INI! -- counterpart).
Truly maddening (not to mention embarrassing) to watch the incompatible divide between .NET and JS continue to be reinforced by MSFT own internal developers.
Pretty cool talk, but Xaml is still not as cool as it was in WPF/Silverlight5. :P
Xaml is an object definition and serialization mechanism, not a "UI platform." It has been completely bastardized in its intent and it is still nowhere near as cool as it used to be. It used to be possible to serialize ANYTHING with it, POCOs included. This is no longer the case.
The fact that this team was seriously considering asking developers to remove bindings altogether from their xaml (!!!!) really just underscores the absolute disconnect from the original spirit and intention of Xaml.