If I were going back to step 0 with a startup today, I would not repeat my decisions to stick with AWS. Their stack is slow-moving and frustrating. The VPC rollout has been a slow motion car crash that is only righting itself in the past 3 months. Meanwhile Azure has amazing management tools and GCE has got well-supported containerization as its primary product interface. Both provide competitive rates and subsidies for small tech business, as well.
Do you have references for the assertion? I'm entirely happy to say I did the tests wrong, I did them as a trio of evening projects.
Thank you.
The DevOps trend, and developer mindshare is paramount regarding their cloud initiatives... Azure AD and Office 365 will keep things floating, but only Azure as a whole will keep it alive beyond XBox...
Microsoft is very good at tracking and keeping with developer mindshare, as well as adapting. They're also a large corporation with many nooks and crannies, so there are exceptions to everything. The change lately is the acceptance that windows is waning... and they have to shore up other areas even at the cost of windows for the larger company to survive... this is a colossal shift that can't be underestimated.
As a result initiatives that may have never seen the light of day around .Net as a whole, VS Code (with great go and node support), and a slew of other nice things coming from MS would never have seen the light of day. I am surprised how much I like using VS Code on OSX, I switched from Webstorm and Sublime, even with some rough edges in es6/7 syntax support. DNX and .Net Core stuff has me considering .Net and Mono again when I'd all but written them off.
I was forced to work with Azure late last year, and after writing some simpler wrappers using some of their APIs have to admit that I liked using them more than AWS. It's really interesting that the less I rely on MS, the more I appreciate the work they've put out there.
Yes, a much more accurate description than the GP's would be that the "new Microsoft" isn't letting single executive edicts set corporate policy for many things, such as how all teams should interact with the open source communities, instead letting teams themselves make that decision and then supporting them in doing so. The natural result is that many developers within Microsoft come from or have extensive experience with open source and so will embrace it when given the opportunity.
It feels like less a change in philosophy of "open source is our future" and more of one that good decisions can come from the bottom up (and a little bit of "yeah, the whole 'linux is a cancer' thing was really stupid").