After the mismanagement of WinRT, finally fixed with UWP on Windows 10, instead of improving the .NET Native and C++/CX experience, they created Project Reunion, deprecated .NET Native and C++/CX, replacing them with lesser tooling, pivoted Project Reunion into Windows SDK, and are years away of reaching feature parity with UWP, let alone Forms, WPF, MFC.
The current team seems composed by interns without experience on previous Microsoft frameworks, while the more experienced folks seem to have moved into Azure, Google or Amazon, from their twitter feeds.
Just have some fun going through the WinUI, CsWinRT, C++/WinRT, WinAppSDK, Win2D, and see the endless amount of bug tickets, measured in thousands.
Blazour seems to be the new kid in town, to the point of even trying to push it inside MAUI as pseudo-Electron replacement.
Meanwhile the other business units are focused on Web or Android.
It looks like "Azure OS" is the new Windows.
That’s my suspicion too. And I believe they did the same thing with Teams and hired some interns who are learning Agile to rapidly deliver “feature”.
At this point, I'd prefer an Azure OS that I could install locally and have the Windows team slowly transition to supporting Wine, improving Linux DEs/Wayland (or even create their own DE), since I believe that they're using some Wayland compositor (mutter?) for gWSL anyways, and contributing to the Linux kernel, which they're already doing to some degree. I genuinely don't know how feasible that is and I'm aware it's wishful thinking, but a person can dream.
Then again, it would probably be to the Linux community's detriment and they'd just do the same scummy Bing/telemetry/dark pattern crap to foster ad revenue.
That just runs completely counter to all the Dev Experience marketing you get from them. It feels like Widgets were slapped together by the kernel team at the last minute.
WinRT is basically the evolution of this, going back to the design board as if .NET never happened, hence .NET Native and C++/CX abstracting what is basically COM + IInspectable + .NET metadata instead of TLB + App Identity.
WinRT eventually became UWP, as they improved the developer experience, only to kill .NET Native, replace C++/CX with C++/WinRT (similar dev experience as using ATL), and move that infrastructure on top of standard COM on Win32 side.
So now you have classical COM, and Windows Runtime components are the modern COM.
Meanwhile DevDiv seems to have had enough of this and decided to focus on .NET with cross platform experience, and Web technologies, hence why even Visual Studio is quite lacking on WinUI tooling.
[0] - If they really cared they would have doubled down on it like Android and ChromeOS did, and all those C# 7 - 11 performance improvements would have been done at the time.
It would become on life support at that case.
Any Apple engineers reading this - an update like Snow Leopard would go a long way!
People don’t care about that. They want the computer to go away and actually stop bugging them.
Other workflows than mine would probably have different results.
I respect people who prefer Macs to PCs, but stop speaking about it like it is some universal truth.
If your gaming doesn't work correctly on an OS other than windows, it is probably the manufacturer fault.
Look, I don't know about you, but I don't have unlimited time to go fiddle with whatever emulation layer is there to make some game from 2017 work well on a modern Mac. Not only that, but Apple has proven, time and time again, that they completely do not care about backwards compatibility, which is crucial for games, so let's not pretend that the "manufacturer" (assuming you're talking about the game developers here) is at fault - nobody has unlimited time to adjust their product on the whims of the folks in Cupertino.
Here's the reality - on Windows, I can still play DOS games. On macOS, with the latest OS release, 90% of my Steam library cannot be used (that were all perfectly fine before the update) because Apple decided to remove support for 32-bit apps. So sticking to Windows for gaming is the logical choice if you want access to the latest and greatest titles and not a selection of a few that are "hacked around".
But the mouse, if it doesn't work and it says it does on the box then that is the vendor issue.
There's awesome Linux experiences out there and the Steam deck is starting to show what's possible giving varying levels of control.
We live in exciting times. The more choice, the better.
Again - not necessarily saying that the Windows experience is ideal, but it's the absolute best out of the available options.
Guess how much malware suddenly can't execute.
On a client machine where the bulk of the software I bought is 32-bit and it stops working overnight, that's less acceptable.
But that doesn't mean it works. It's literally only there because it is entrenched. A lot of the time it doesn't work and has an extremely large support cost.
We see this with Windows and with MacOS. MacOS's downfall is the more visible one.
The OS is no longer prioritized except where it needs to be somewhat presentable in screenshots. The OS becomes a vehicle to sell company goods. The OS rots to the point that there's no one left at the company with even the most basic competence to create first-party apps for it.
Because the money is elsewhere.
I wonder at which point this neglect makes the OS so unusable that it actively hurts the development of the money-making machines.
Though strangely enough MS would survive this better than Apple.