4 ms·
UWP is about 10 years or more too late. C++/CX is a dialect of C++ that has refcounted pointers (like COM). It is much better than the (also proprietary) exten
by captainmuon 9y ago
UWP is about 10 years or more too late.
C++/CX is a dialect of C++ that has refcounted pointers (like COM). It is much better than the (also proprietary) extensions for COM to C++ MSVC had decades ago, and it is also much better IMO that managed C++ and C++/CLI. Of course, in a way it is still a hack. But I read that MS is also working on a way of doing managed components in modern C++ (i.e. 11/14/17). MS is doing a lot of great work in the area of modern C++ lately (surprisingly to me).
And UWP is yet another incompatible version of XAML/WPF/Silverlight/.... I don't like the castrated nature of it, it is incredible simple things are hard or impossible (like cross process drag and drop, which is not supported even in MS Office store apps. Or any kind of IPC, or networking with localhost). But things are getting better, as MS removes the worst pain points and developers learn to circumvent the missing parts.
One thing that seems great in UWP is it's async-first approach. I learned to appreciate that paradigm with Python/Twisted and JS.
So it's not all bad. If Microsoft had UWP 10 or 15 years ago (in their "Avalon" phase) it would have been great. Now, it's just "meh".
- frik 9y agoIn an alternative reality were DotNet never happened and MS evolved Win32API with COM (so basically continue the strategy of 1989-1998 until the great break with DotNet happened), yes then a new "Win64API" with modern C++ would have been great. But the Web happened, DotNet original vision failed, their pivoted vision was declared as legacy 5 days ago too, and UWP failed with no one buying their Win10phone (0.02% global market share).