You might want to look at the UWP version of XAML. It has really useful things like compiled bindings (x:Bind), calling functions as part of a binding with automatic change detection of the function params (x:Bind only), x:Phase for progressive enhancement during scrolling, StateTriggers, and Setters for visual states (consolidated VisualStateManager and Triggers).<p>Not to mention the interop with the amazing Windows.UI.Composition API's, which let you do expression animations, Direct2D effects, lighting, parallax, backdrop brushes (e.g., blur the content behind an element), etc.<p>WPF's version of XAML feels quite dated now.<p>Also, doing layout on the UI thread is a severe perf limitation that currently affects all versions of XAML. Consider having the UI framework just specify constraints and letting the compositor/render thread compute the absolute positions ;)
Does anyone have a prediction when .NET Core will be extended to include UI? I find this lack is the most confounding aspect of MSFTs strategy. Is Xamarin really it?