Comment by SigmundA
11 years ago
XAML != WPF. XAML is a language for object instantiation, thats it. Similar to XIBs in the Apple world.
There are no less than 3 similar but different and incompatible UI libraries that can be instantiated by XAML: WPF, Silverlight (WPF/e), and Windows store/phone (WinRT). WPF is dead like WinForms but the only solution for normal windows apps unless somethings changed with WinRT to make non full screen apps with.
If you have ever tried to develop across more than one of these with a shared code base you will know how frustratingly similar yet how incompatible and different they are. They are not supersets or subsets they are forks.
Windows 8.1.1 allows non-fullscreen WinRT apps.
So yeah, when I said WPF, I meant XAML/WinRT. My main desktop use is supporting WinForms legacy apps so I don't keep up with the new GUI frameworks.
If you want to write a dev tool, WinRT doesn't cut it due to window store restriction and we are stuck with WPF. WPF also contains many features missing in WinRT, which is probably why it's still more popular than.
I'm looking to move to direct2d eventually. I work at a low enough level that this wouldn't be too bad for me.
Why would they do this? The cycle of new frameworks only to be killed again afterwards is frustrating.
Is everything just wrapped around Win32 like MFC was etc.?