|
|
|
|
|
|
by david-cako
1874 days ago
|
|
|
Microsoft has been around a long time and they seem to adapt pretty rapidly. I wonder what percentage of the company today was around during Ballmer days, and how the culture has changed over time within the company. Naturally it's going to be driven by the market, but I wonder, are older MS folks moving with the culture shift? Or is it newer hires that are pushing for the open source ethos? As a Mac and Linux user, I really like Microsoft these days. VSCode, WSL, Rust, containers, Surface, .NET Core, all are pretty sweet. |
|
|
When AWS first blew up they sort of struggled in European Enterprise because they originally went Google route or automating everything while taking a “our way or the high-way” attitude toward legalisation and localised agreements. This is basically why Azure was capable to fill the void that AWS was struggling to fill. Modern AWS has learned a lot from Kim that though, and are now ahead of Microsoft in many areas. I still can’t get a guarantee that only European citizens working in the EU will be the only people who work on my Azure cloud like I can from Amazon.
But as a whole, the sort of setup where I can call Redmond directly when shits hit the fan, and they will even give me hourly updates via phone until the issue has been resolved. That’s a Balmer sort of thing. And so is the financial aspect of how much more sense it makes to chose the Microsoft option once you’re already in bed with them. If anything that last hit has only grown under the new Microsoft.
I mean, how can I justify to my political leadership that I need to buy a Microsoft Teams competitor when it’s already included in our office365 setup? I can’t, and this just snowballs over time.
I’m not unhappy about this by the way. Through the past many decades Microsoft has been one of our best business partners as far as Tech goes. Which is very likely why AWS has adopted the approach.