4 ms·

> It does seem like things have settled down upon UWP finally They officially cancelled UWP 2 months ago, after a few years of "not quite dead, not actively su

> It does seem like things have settled down upon UWP finally They officially cancelled UWP 2 months ago, after a few years of "not quite dead, not actively supported" limbo. I guess it's settled down, but not in a good way. https://www.theregister.com/2021/10/26/microsofts_uwp_unwanted_windows_platform/ https://www.theregister.com/2021/10/26/microsofts_uwp_unwant...

dragontamer 5y ago
Hmmm. I thought the migration path between WinUI 2.0 (aka: UWP) and WinUI 3.0 was easier. Looks like Microsoft screwed the pooch one more time for one more upgrade cycle. Why do they keep doing this? They really need to think about code compatibility for more than a couple of years. Its not like Android or iOS developers need to deal with 3+ migrations over the past decade.
- ryandrake 5y ago
  I left Windows programming around 2006 or so, when it was Win32 and maybe MVC if C++ was your thing. Recently was noodling around with the idea of porting one of my hobby projects to Windows, and a just can't believe the mess the platform has become! Now we have Windows Forms, dotNet, WPF, UWP, WinUI, and probably a dozen more. What API should I use to "get back into Windows"? Will it be deprecated next year? If I pick the wrong one, and drive the train down those tracks for a few months, am I basically throwing all the code away? What an absolute mess!
  - thrower123 5y ago
    WinForms is the one to pick if you want something that will work forever and always be supported.
    - tonyedgecombe 5y ago
      It's not great though unless your requirements are rudimentary. I wasted a huge amount of time on supporting high-dpi. The architecture is archaic.
  - ripley12 5y ago
    Based on everything I've seen in the last year and a half: WebView2 (i.e. Chromium) is getting more investment from the Windows team than any of the "native" UI technologies. I'm not thrilled about it but I'm adjusting my plans accordingly.
- ripley12 5y ago
  > Why do they keep doing this? I can speak to the UWP -> WinUI 3 transition a little: it's a hard transition because UWP did so many things its own way. It's often really difficult to migrate concepts from UWP to the Win32 app model. And I get the impression that the number of people working on WinUI+WASDK is pretty small; it's more of a "salvage what we can" operation than a "build out the future of Windows app development" one.

dragontamer 5y ago

Hmmm. I thought the migration path between WinUI 2.0 (aka: UWP) and WinUI 3.0 was easier. Looks like Microsoft screwed the pooch one more time for one more upgrade cycle. Why do they keep doing this? They really need to think about code compatibility for more than a couple of years. Its not like Android or iOS developers need to deal with 3+ migrations over the past decade.

ryandrake 5y ago
I left Windows programming around 2006 or so, when it was Win32 and maybe MVC if C++ was your thing. Recently was noodling around with the idea of porting one of my hobby projects to Windows, and a just can't believe the mess the platform has become! Now we have Windows Forms, dotNet, WPF, UWP, WinUI, and probably a dozen more. What API should I use to "get back into Windows"? Will it be deprecated next year? If I pick the wrong one, and drive the train down those tracks for a few months, am I basically throwing all the code away? What an absolute mess!
- thrower123 5y ago
  WinForms is the one to pick if you want something that will work forever and always be supported.
  - tonyedgecombe 5y ago
    It's not great though unless your requirements are rudimentary. I wasted a huge amount of time on supporting high-dpi. The architecture is archaic.
- ripley12 5y ago
  Based on everything I've seen in the last year and a half: WebView2 (i.e. Chromium) is getting more investment from the Windows team than any of the "native" UI technologies. I'm not thrilled about it but I'm adjusting my plans accordingly.
ripley12 5y ago
> Why do they keep doing this? I can speak to the UWP -> WinUI 3 transition a little: it's a hard transition because UWP did so many things its own way. It's often really difficult to migrate concepts from UWP to the Win32 app model. And I get the impression that the number of people working on WinUI+WASDK is pretty small; it's more of a "salvage what we can" operation than a "build out the future of Windows app development" one.