4 ms·
MFC, UWP, WPF, WinForms etc. I wonder how long before this is superceded in turn? My 3 applications are written in Qt/C++. Hopefully it is going to shield me f
by hermitcrab 7y ago
MFC, UWP, WPF, WinForms etc. I wonder how long before this is superceded in turn?
My 3 applications are written in Qt/C++. Hopefully it is going to shield me from this, as it has from the previous changes.
- toyg 7y agoYeah, MS has been very inconsistent of late. They went from Chen-style decades-long support for foundational tech, to a whirlwind of different things, promoted then chucked aside like they were a Google product.
- MaxBarraclough 7y ago> then chucked aside like they were a Google product. They're still supported though, right? (WinForms, WPF, UWP.)
- stev_stev 7y agoYes. UWP already mostly uses WinUI 2.0 I think. 3.0 will expand the minds of applications that can make use of the component library and provide a way to gradually incorporate newer controls into older technologies (WinForms, WPF etc).
- toyg 7y agoYeah but at one point the future was WPF, then it was Silverlight, then it was Javascript...
- MaxBarraclough 7y agoSure, they keep inventing new GUI toolkits for little reason, but unlike Google, the old ones can still be relied on.
- nxc18 7y agoNot really, a bunch of apps from the WinRT era are very broken under Windows 10. It’s disappointing given how much from the early 90s still works, but code from 2013 is now totally broken.
- int_19h 7y agoSilverlight is where things have started to go downwards wrt long-term stability. But Win32, MFC, and WinForms are still very much alive and well. I mean, WinForms even got .NET Core treatment and high/dynamic DPI support.
- noobdood 7y agoAnd MFC was on top of the Win32 API/SDK.
- stev_stev 7y agoUWP and Win32 apps will be able to make use of the WinUI components, so I think this is at least a better approach going forward.