MicrosoftRickLord It would be very technically difficult to feature a feature or content aware switch that suggests a change only when new software is deemed to have feature parity or feature equivalency.
I’m not saying that MSFT can’t do it. I’m saying it would be very technically challenging for very little fruit that it would yield. Because MSFT demonstrates that they only are concerned that enough of the target group of people accept a move. They don’t even have to love the change, just accept it silently. And there’s a lot of those people. MSFT just needs to hit that mark.
So a feature or content aware update path is too high resource, low reward for that. The second problem with this critique is that even if MSFT could roll it out in that manner, you’re forgetting that MSFT doesn’t want the user base to stay in “Classic” Outlook.
Outlook365 desktop client is an albatross for the engineers there. They are dead set on web-ifying everything that they can. It lets them build the bulk of the stack code in one place where eyes can gain access from the most devices, the web. And then they can customize and port to the other two platforms they officially support, Windows and MacOS.
And with the web based code they can jam in their half baked Microsoft Copilot, and charge a premium for half-assed, Fisher Price software for the children of the workplace and their technically illiterate cohorts who can’t tell the difference.
This isn’t meant to be a software update to bring an alternative to those who are lite mail users or who want something standalone that mirrors Outlook.com. This is the replacement. They don’t care about whether you want it or like it. They don’t care if it inconveniences you or leaves you behind. Otherwise why would they forcibly install this software on Windows and if you uninstall it, reinstall it without your permission, again?
