Thread by @QuinnyPig

Okay, let me break my own rule and put on my Prediction Pants for a minute.

The day @GitHub gets a "deploy to @Azure" button that Just Works @awscloud is going to find itself in serious trouble.

https://twitter.com/chetanp/status/1344069195604971520

I don't see what @chetanp does with respect to GCP, but it's a mighty big industry. I suspect we're both pawing at different parts of the elephant.

The single biggest impediment to @azure near-term looks like Old Microsoft playing stupid licensing games to win stupid prizes.

But consider this for a second: You're a developer puttering around in your idle hours. Your @azure free tier resources / limits are a function of your @GitHub activity (social or otherwise). Suddenly it's gamified and profoundly compelling.

So now you start a project in VS Code. It automatically populates your Git repo with the scaffolding, creates a GitHub repo, instantiates CI/CD, provides a "put sensitive creds here" dialogue, and your MS contract already covers all of this so it's Enterprise Frictionless.

I've now got dev, staging, and prod environments / resources for your repo that live on @Azure. If I'm Random F500, I have significant spend with MS already. So I can realistically move everything to @GitHub and Azure immediately with very little work by Procurement and Legal.

And @awscloud's product superiority will only carry them so far (and in the fullness of time is likely a transient advantage). I can't figure out why AWS is squandering its early lead so cavalierly.