| I think what's more likely in this case is that MS under Satya really does want to be a good corporate citizen, but are finding themselves in a bind that threatens the whole organisation. They're spending up the wazoo on Xbox, still, to battle PlayStation. They were supposed to have conquered that market over 15 years ago and are still throwing money at it. Windows is hurting as a retail business. License costs have been driven down by Chromebooks and resurgent Macs, and with all the free upgrades they get very little revenue from gaming PCs anymore (which is one of their biggest markets) while also battling Proton and Vulkan to keep users on the platform. That leaves Azure and Office as the big cash cows. Azure is struggling to compete with AWS, and the big draw of Azure is the deep integration between it and Visual Studio (which, to be fair, is unrivalled anywhere else). That's the bind. Microsoft needs the open-source community to embrace Visual Studio Code, and they have, but they also need to protect Azure's hegemony with .NET developers. Can you build and deploy .NET on other clouds currently? Of course. Do you lose a lot of features by doing that? yes. Ones you may miss, or (if you've never been on Azure to become familiar with them), ones that may draw you to migrate later. |
> MS under Satya really does want to be a good corporate citizen
... followed by...
> [a bunch of reasons why MS won't be a good corporate citizen]
Wanting is great, but actions speak louder. Maybe instead of doing sketchy things to try to lock people into your cloud platform (and make using your framework on other platforms more difficult), they could, I dunno, maybe focus on Azure itself, and making it better than AWS? The world would be a better place if companies were incentivized to compete on product features, and not through shady practices and backroom dealing.