![]() ![]() Yet for a while Midori was even responsible for powering parts of Bing. Joe Duffy has a couple of remarks on his talks about those efforts, where he mentions even with the platforms running in front of some responsible people on Windows team, they were sceptic of its capabilities. What killed Longhorn wasn’t technical issues, those could have been solved if the teams worked together, as proven by Singularity and Midori projects. It is hard for such things to take off, when the Windows team (responsible for Windows/C++) makes an active effort to sabotage the work from DevTools team (responsible for. The next iteration of C++/CX (or WinRT) was slightly better, but still not good enough.” Net/C# APIs, which unfortunately did not take root. There are many modern issues like Hi Dpi displays, multiple displays, remoting, security, and so on that are tough to do, would benefit from a real positive overhaul. People want to run Win32 as much as possible, and as long as Windows supports Win32 natively no other toolkit seems to be able to displace it. The leaves Microsoft in a tough position. Moving everything to HTML was tried (in early Windows Start Menu apps, and now with Electron and others). The main being having different User Experience paradigms (i.e.: they don’t ‘act’ the same). “Foreign” toolkits, like GTK or QT run okay on Windows, but they have highly observable issues. The next iteration of C++/CX (or WinRT) was slightly better, but still not good enough. Even though this is almost always abstracted by a UI framework, it still causes issues. ![]() The program needs to keep track of many essentials (including simple things like moving the window, or dispatching timer events). Win32 API is “inelegant” when compared to modern alternatives (or it can be seen as “from a more civilized age” as being very low level). They’ve tried to put full Windows on phones – twice! – and nobody wanted that either. They’ve been trying to just kind of coast by on Windows 10, and as the above article notes, it’s been quite problematic. They tried combining the two into one with an adaptable UI – and everybody hated it. ![]() ![]() They’ve tried creating a version of Windows only capable of running ‘modern’ apps, and it failed – twice (and a third attempt is on the way). How much freedom to push the Windows platform forward do you really have when all users want is to run the same set of Win32 applications in perpetuity? They don’t want ‘modern’ apps forced upon them, they don’t want touch-optimised user interfaces, they don’t want application stores, and they certainly don’t want Windows anywhere else but their desktops and laptops. It seems most Windows users want Windows to just be… Windows. That’s a lot of reshuffling, but I wonder what the purpose of it all really is. We’ve seen plenty of evidence of that with a messy development experience for Windows 10, delayed Windows updates, a lack of major new features, and lots of Windows update issues recently. It’s an admission that the big Windows split didn’t work quite as planned. Specifically, that means the Windows fundamentals and developer experience teams have been returned to what we traditionally call the Windows team. Now, Microsoft is moving parts of Windows development back under Panos Panay’s control. Microsoft moved core Windows development to a cloud and AI team (Azure), and created a new group to work on Windows 10 “experiences” like apps, the Start menu, and new features. It follows Microsoft’s decision to slice Windows into two parts more than two years ago after the departure of former Windows chief Terry Myerson. The software giant placed Surface chief Panos Panay in charge of Windows earlier this year, and is now reshuffling parts of that team. ![]()
0 Comments
Leave a Reply. |