7

Is it just me or has Windows SDK gone down hill horribly in recent times
WPF -> UWP was a giant and good step
then they kinda killed off UWP, focused on XAML Islands

then came Windows 11 which breaks some UWPs built with WinUI2 coz the components are tied to the OS and not self-contained, so some dont exist in Win11 and the apps crash on runtime

Now there's WinUI3 but it assumes that the starting point is Windows 11, I try to build em on Win10 (coz win11 sucks ass), and intellisense it all crazy

These are all issues one can circumvent IF they align their setups the way MSFT desires
But the fact that these issues exist and wont work out of the box, makes me wonder how long before they start recommending Electron or some other "JS/TS-based UI framework" that'll work within ChakraCore or something. Getting back to WPF/Win32 days

Comments
  • 0
    The Windows API has always been kinda shitty. I try to use something that abstracts that interface across platforms.
  • 1
    @Demolishun hmm :/ I like native, but seems like its future is bleak
    at least compared to what it was before
  • 1
    Abolish recent WinUI toys; return to Windows Presentation Foundation on .NET 4 and Mono.NET
  • 2
    @azuredivay native UI is great but MS is constantly fucking it up. As soon as something becomes actually good, they deprecate it and replace it with something new, similar but not compatible.
  • 2
    UWP was amazing, on one side WinUI is not ready yet compared to UWP, also because the team is small...and on the other side they put lot of resources on slow, heavy, pen&touch unfriendly web based tech... It's a nightmare, I love native apps
  • 3
    @Lensflare about UWP dead we have to thanks lot of press and users screaming UWP bad without even know anything
  • 2
Add Comment