Not sure what this is a reference to. Microsoft STILL supports running VB6/COM/C++/etc from the 1990s today. Only Visual J++ disappeared, but a court of law required that. I'd go so far as to claim that their success is in no small part because their backwards compatibility game is top notch.
IE6 was a nightmare, but that wasn't "pulling the rug" rather just being lazy and not developing the browser at all (because it competed with their proprietary platform -- Win32). Once Microsoft deploys something and developers start using it, typically they support it "forever" (even IE compatibility modes remain to support IE5/6 code).
I tend to prefer software that works everywhere I do. I use Windows, Linux and Mac on a daily basis. Though haven't done desktop Linux in close to a decade at this point (next desktop will likely change that).
On the flip side, I actually appreciate that MS has done a number of apps with web and electron focus. VS Code shows you can do a well performing editor in a browser, I almost didn't even try it after atom and brackets. That it's on all three, I really appreciate. WTF the Teams app isn't available on Linux irks me to no end. The Azure SQL Studio is also progressing nicely. I also happen to like the relative ease of using Azure's services, but it's more than I'm going to pay on hobby projects.
The root issue was that Microsoft preinstalled the (free) Internet Explorer at a time when other web browsers were commercial. Netscape Navigator in particular was free for personal use, but Netscape wanted a fee for business use.
That was the original sin of the monopoly: Microsoft used its dominance in the operating system market to take over the browser market at a stroke. They compounded on this with "embrace, extend, and extinguish" practices, where they would introduce and maintain IE-only web extensions to the detriment of existing and upcoming standards.
You still see the modern legacy of this with Internet Explorer 'compatibility mode' hacks, since it turned out that Microsoft itself became stuck in its own morass.
There's no reason Apple should be allowed to force Safari exclusively on iOS. We had an entire anti-trust decision about this - https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor.... It should be bog-standard-illegal, and Apple deserves an equally bad rep for this.
* Using secret API calls to make sure their software ran faster than the competition. If you had a database server or spreadsheet application you could had a myriad of choices in the early 90s but the fastest, stablest one was always from Microsoft.
* OEMs could not change the default browser. Even when given money to install an alternative the default OOB browser was required to be IE.
Early Macs had no browser at all and at <5% of the PC universe they had no monopoly status. Before Safari Apple used MSIE as the first browser. Firefox and Webkit weren't ported over until ~2005. And long before the Apple App store the only application on iOS1 and 2 was the browser. It didn't have apps as we know it today. It would be hard to prevent them from including the browser since it shipped with the device day 1.
[0] https://en.wikipedia.org/wiki/Millennials#Date_and_age_range...