I personally still use WPF for all my development given its richer API. I'm not a big fan of XAML, but WPF has a good basic API for putting stuff on the screen and handling input in C# (disclosure: MS employee, but research).
Only those not able to grasp that what matters is the XAML stack, not the little layer that is put on top of it.
I really wish JavaFX Script would have taken off. It provided a nice balance between code and markup.
I just tend to abbreviate to XAML when speaking about it.
There changes on the APIs between WPF, WinRT and Silverlight if you will, and not all features are exposed across all stacks.
Yet, any developer knowing XAML, the usual programming idioms and the respective .NET APIs can easily transition among all of them.
This has been mentioned at multiple PDC and BUILD conferences in the last years, but I guess many at HN and Reddit don't follow them.
Plenty of Microsoft haters on HN, this post has already been flagged or flamed off the front page. Oh well.
Parts of it eventually became what is known as WPF. The whole set of concepts that it embraces are as follows:
- XML based "language" for describing UI layouts (XAML)
- A set of .NET APIs for buttons, dialogs, windows, and so on
- A set of .NET APIs for manipulating the XAML DOM
- A set of .NET APIs for handling application resources
- A set of abstraction concepts, namely binding, data templates, triggers, MVVM, storyboards
When Silverlight came out, the team responsible for it adapted all these concepts to the platform. Similarly to the WinRT platform.
The main differences are the XML namespaces used by XAML, which expose different set of UI widgets in each platform.
Also some .NET APIs are a bit different as the classes aren't 100% equal across all platforms, e.g. TypeConverters are not available in WinRT.
However those basic concepts originally from Avalon are still there.