Thread by @Nick_Craver

This is worth repeating:
We're migrating Stack Overflow to .NET Core. **It's not because of performance**.
There are enough major wins without even factoring performance for us to move. Any performance gains are 100% in the bonus category. We'd migrate with a 0% perf improvement.

https://twitter.com/Nick_Craver/status/1031857965198991360

Some problems we face today:
- Testing as much as we want
- Using new features of .NET without waiting on customers to approve each .NET 4.x system version
- Deploying a container/VM with SQL Server
- Deploying a single container/VM with Redis
- Endless .csproj conflicts

Other things like middleware can replace app pools we have to handle other tasks today. It'll simplify our deployment.

Testing is *huge*. And not only code tests. We'll be able to spin up the whole SE network "in a box" for every PR and test it properly to poke for UX, etc.

Our main .csproj will go from 13,000+ lines to ~100. I hope that's an obvious win. Deploying one container or VM instead of many for our Enterprise install is huge for easy deploys, upgrades, and trials. Upgrades we could make self-service. Fewer permutations; less to support.

Customers in Azure? What if we had one way to deploy testing, on-prem, and hosted for Enterprise? Or at least very few ways of assembling the same LEGO pieces. That's what .NET Core is. It's very modular and enables a litany of wins for us.

So we're moving. Perf is just a bonus.