"many flavors of XAML"
This is where things went HORRIBLY, HORRIBLY, WRONG.
A couple of quotes from the article:
"Developers who have followed the twists and turns of Microsoft's developer story over the years will know that there are many flavors of XAML"
"There are WPF XAML, Silverlight XAML, and UWP XAML, all different"
sort of like "you are in a twisty little maze of passages, all different" (from a version of RJR Cave that had the batteries in a vending machine within the 'all different' maze).
Did Micro-shaft *MISS* *THE* *BOAT* on this? If we wanted an XML-based UI description, then there's already a simple way of doing it: HTML FORMS. Like web pages, only internal to the application. I'm pretty sure that Webkit has a means for doing this...
There's a somewhat-nice implementation of this for Android. I made use of it once to display a web server's screens as *IF* they were an application running on a slab to control a device. [it was a nice rapid hybrid prototype solution to the problem of getting a GUI on a 'droid slab to control stuff on an Arduino over a serial cable, while displaying live video capture and controlling tests in real time]. The wrapper Android application was pretty simple. All of the work was done on a custom-written Linux web server. [it went into clinical trials that way, being a device associated with certain kinds of eye exams].
So with Java sitting pretty at the top of the TIOBE index for the last SEVERAL YEARS, why is Micro-shaft *BOTHERING* with their C-pound ".Nut" "solution" for cross-platform, with XAM-IT-UP-YOUR-BACKSIDE for GUI screens?
Simple: they want to CONTROL THE DIRECTION for software development. More like DRIVE it, like cattle across the plains, heading for the slaughterhouse. THEN, their PATENT ENCUMBERANCE will keep OTHERS from competing, in THEIR playground, by THEIR rules.
No thanks.