3 ms·
>In the Microsoft land it's always utterly confusing to get started. You are always left guessing what choice to make. Not it isn't. What you're pointing out i
by Rinzler89 2y ago
>In the Microsoft land it's always utterly confusing to get started. You are always left guessing what choice to make.
Not it isn't. What you're pointing out is the PRO of Windows, not a CON. It's why backwards compatibility works so well. If you have a super old app you're still developing, you can keep using that old UI stack, no need to rewrite it on a newer one just for ti to be compatible with the latest Windows release.
I feel like most people complainant about the different UI stacks supported by Windows, are not Windows developers but just enjoy pointing it out as if it bothers them somehow through sheer existence even though they never wrote any Windows apps.
- pjmlp 2y agoThe Windows developers community are pissed off with how badly WinRT was managed since Windows 8. There is seldom anyone of us that went through that, and will advise anyone to use WinUI 3.0, unless they themselves have a sunken cost into UWP, and need a way out. Quite easy to find out in the endless discussions on the related Github repos.
- Rinzler89 2y agoBut you aren't forced to use Windows RT. Why does its existence bother you? >Quite easy to find out in the endless discussions on the related Github repos. People on the internet complain about anything. How many discussions are there about Gnome's file picker?
- pjmlp 2y agoBecause like many in the Windows developer community, Microsoft has ripped us off with all the mess they have made with WinRT since 2012, multiple rewrites, broken tooling, dropped features. And worse of all, in the end, those of us doing WinRT advocacy, were the ones answering for Microsoft's missteps in customer meetings. Too many hard feelings to let it go just like that.