3 ms·
If they were being held back by the "legacy" parts of the OS, you might be right. But they're not being held back, rather, it's their unique selling point.. Ar
by quincunx 9y ago
If they were being held back by the "legacy" parts of the OS, you might be right. But they're not being held back, rather, it's their unique selling point..
Arguably the legacy bits are the bits that work, the modern bits (UWP) are barely seeing any adoption. They're force feeding the modern bits, presumably because they've lost the human resources/mindset/talent to maintain the legacy bits?
This strategy of arm twisting coercion has failed them before and it will fail them again, and again, and again.
- watmough 9y agoYes, look at the bits used by Microsoft Office ... Win32. I could believe the flashing (when running over RDP), glitchy, sluggish Outlook 2016 is using some of the new stuff. It's not a success in my view.
- DougN7 9y agoOffice 2016 really sucks compares to 2013. It feels like a browser app. Is it UWP?
- gt_ 9y agoI feel this way too. The old shell is bad but I still prefer use it over Powershell. The Windows store stuff and feels like a flat joke that just never ends.