It's kind of a drag seeing all this re-emphasis on Wpf at this time. When UWP started being released, it was painful to witness the extent to which Wpf was being ignored. Now Microsoft is doing the same with UWP.
I guess the Silverlight fiasco wasn't enough of a lesson. The UWP Sandbox and App Store were generally the right direction had reasonable compromises been made. All that really needed to be protected on the file system were the Windows and Program Files (xxx) and Users folders. The rest should have been left unrestricted thus, a lot of dev grief would have gone away.
The way the file access futures list works at present is a mess (the UWP Ziparchive being a prime example of the dysfunctional way this works), which just serves to highlight the extent to which there's no intent within Microsoft to get this right.
The use of restricted capabilities is now pervasive within Microsoft's apps, which further highlights how crippled Microsoft felt when creating UWP apps.
Rather than doubling down on UWP and fixing what's wrong, Microsoft is now doubling back to Win32. Wow??
I met with some of you folks last year and had a feeling "this" was the direction the wind was blowing. You're listening to the wrong people. The WinRT API should be THE API. It's Win32 that needs to go away, likewise with WPF. Resurrections have nasty way of bringing back the dead and dying. Perhaps the zombie apocalypse is coming.
It's kind of a drag seeing all this re-emphasis on Wpf at this time. When UWP started being released, it was painful to witness the extent to which Wpf was being ignored. Now Microsoft is doing the same with UWP.
I guess the Silverlight fiasco wasn't enough of a lesson. The UWP Sandbox and App Store were generally the right direction had reasonable compromises been made. All that really needed to be protected on the file system were the Windows and Program Files (xxx) and Users folders. The rest should have been left unrestricted thus, a lot of dev grief would have gone away.
The way the file access futures list works at present is a mess (the UWP Ziparchive being a prime example of the dysfunctional way this works), which just serves to highlight the extent to which there's no intent within Microsoft to get this right.
The use of restricted capabilities is now pervasive within Microsoft's apps, which further highlights how crippled Microsoft felt when creating UWP apps.
Rather than doubling down on UWP and fixing what's wrong, Microsoft is now doubling back to Win32. Wow??
I met with some of you folks last year and had a feeling "this" was the direction the wind was blowing. You're listening to the wrong people. The WinRT API should be THE API. It's Win32 that needs to go away, likewise with WPF. Resurrections have nasty way of bringing back the dead and dying. Perhaps the zombie apocalypse is coming.