When the answer to your tech problem is not ASP.net/SQL Server, you are going to find their services much more difficult to put up with compared to the competition.
Before someone jumps in with ".Net is huge in the X space" thing: There has been double digit growth of close to a decade now of platforms that don't run .Net. That ecosphere was a giant. Now it isn't.
As you do this, I personally think that you are much better off getting the JetBrains all-in-one subscription (if you can afford it) over continuing to use Visual Studio. There are a lot of things happening on the data science front which are just that much harder to do within the MS stack.
Actually I really love the C# language, and wish there were .NET ports for Solr, Hadoop and NLP libraries etc. But it just makes more sense to get into the native ecosystems for these libraries (Java, Python etc.) with the most convenient IDEs for those languages (e.g. IntelliJ, PyCharm) and not struggle with trying to get all your NuGet ducks in a row.
[1]: http://thenextweb.com/dd/2016/07/14/amazon-buys-cloud9-aws/
a cloud based IDE is certainly lighter than VS. the fact that it's accessible anywhere is a huge plus.
I would still like to see a desktop version of C9, sort of like Atom & Microsoft Visual Code.
It's going to be hard to justify using Google Cloud after this when I know I'm most likely to ditch Azure in the process as well.
https://cloudplatform.googleblog.com/2016/10/introducing-Goo...
However, Google Cloud really hasn't entered my mind as much as Azure has this year. AWS has always been there. I'm not sure as to why this is maybe I have built a perception that GCE is more expensive and my documentation experience with Google wasn't anymore smoother than AWS.
One thing for sure, Build 2016 earlier this year was one of the key driver for my conversion + Nadella's leadership.
Google Cloud has always been obscured by AWS and now Azure in my mind and so far, they've yet to really jump out at me like AWS does on HN regularly which Azure is now catching up.
This takes a huge cognitive load off the developer who won't have to do context switching between portal.zure.com and VS.
But portal.azure.com is a much better, smooth, streamlined & intuitive interface than AWS, and I find myself wanting to work with Azure more and more.
There is still a stickiness to AWS and stuff like Cognito seems way more less intrusive from brand point of view (MS AD redirects you to onmicrosoftonline.com when logging in user)
Ah, the interface that makes you scroll in all 4 directions on a small screen. I get slightly dizzy using it.
If you told me to use Azure two years ago I would've laughed you out of the room. But here I am in 2016, using Azure, using ASP.net + IIS on Visual Studio. that's some powerful shit and currently AWS has cost leadership and perceived switching cost as their edge.
By introducing a layer of learning curve, you lock in your customers but eventually the other guys will race to lower that curve.