Next to Silverlight, Managed DirectX, XNA, DirectX 12, MFC, WinForms, dotNetCore1, WPF, COM, ActiveX, MSHTML, ATL, WTL, WIC, GDI, GDI+, Direct2D, Direct3D, DirectSound, and so much more, it's not even funny.
And their Store is a broken piece, that no one likes to use.
Basically everyone still uses WinAPI 64bit applications and was most happy with WinXP and now Win7. Guess what Microsoft develops completely against their core user base and ships out waste after wasted efford no one cares about at all.
Someone should scrap all their 2012 to 2017 shit and fork of from Windows 7 and Office 2010. It worked out great back with Windows Vista/7, when it was clear that "dotNet UI based Windows Longhorn" failed spectacular Ballmer scrapped everything dotNet based and started from scratch based on Windows 2003 Server and Windows Vista and especially Windows 7 turned out great, as did Office 2007 and especially Office 2010. The longer they wait, the uglier and more impossible it will get - they are digging their own rabbit hole right now.
Developing desktop apps is hard. I'm working on an open source project [1] that aims to take away much of the pain mentioned in the article, such as code signing. Perhaps some people in this thread will find it interesting.
Author neglected to mention the absolute pain of using any C lib. Everything has to be compiled for UWP and some basic capabilities are/were not available for a long time. Like no access to a secure RNG. Good luck using ffmpeg or libsodium.
One of the reasons Electron is popular is because there are no good choices for Windows. All you can do is choose between different flavors of shit.
Gee, 2 things that I don't want - now without each other!
Why should anyone would go out of their way to build a UWP app? There's no motivation like what Apple has with iOS. If Apple had come out with 2 kits to build apps, one that is restricted like UWP and one that isn't, I don't think we'd see any developers using the restricted kit.
Nope, I'll take Win32 all day long over UWP. Even Microsoft didn't use UWP to build their precious new VSCode editor that they're pimping so hard. They used Electron! Hah!
6 comments
[ 3.4 ms ] story [ 23.3 ms ] threadThat’s definitely not the article’s title. @dang or other mods, can we get this corrected?
I hope @dang can retitle it.
Next to Silverlight, Managed DirectX, XNA, DirectX 12, MFC, WinForms, dotNetCore1, WPF, COM, ActiveX, MSHTML, ATL, WTL, WIC, GDI, GDI+, Direct2D, Direct3D, DirectSound, and so much more, it's not even funny.
And their Store is a broken piece, that no one likes to use.
Basically everyone still uses WinAPI 64bit applications and was most happy with WinXP and now Win7. Guess what Microsoft develops completely against their core user base and ships out waste after wasted efford no one cares about at all.
Someone should scrap all their 2012 to 2017 shit and fork of from Windows 7 and Office 2010. It worked out great back with Windows Vista/7, when it was clear that "dotNet UI based Windows Longhorn" failed spectacular Ballmer scrapped everything dotNet based and started from scratch based on Windows 2003 Server and Windows Vista and especially Windows 7 turned out great, as did Office 2007 and especially Office 2010. The longer they wait, the uglier and more impossible it will get - they are digging their own rabbit hole right now.
[1]: https://github.com/mherrmann/fbs
One of the reasons Electron is popular is because there are no good choices for Windows. All you can do is choose between different flavors of shit.
Why should anyone would go out of their way to build a UWP app? There's no motivation like what Apple has with iOS. If Apple had come out with 2 kits to build apps, one that is restricted like UWP and one that isn't, I don't think we'd see any developers using the restricted kit.
Nope, I'll take Win32 all day long over UWP. Even Microsoft didn't use UWP to build their precious new VSCode editor that they're pimping so hard. They used Electron! Hah!