GitHub after Microsoft: How it has changed
infoworld.com
infoworld.com
Sure, but git repo hosting is a commodity, unlike, say, controlling the Java ecosystem. The full code and history is maintained on all developer machines (at least for the master branch), and the metadata like issues, PRs etc. can be easily migrated off to GitLab.
Doing it before is just premature optimization.
GitHub feeds into that. I'm certain we'll see a "deploy to Azure"-like integration soon.
The 'then' part of that sentence is the issue. It isn't then.
Microsoft are about keeping developers on the Microsoft stack happy. Historically they don't want anyone using any other stack, so they don't want developers making things for other stacks.
Now that Microsoft is moving from selling products to selling cloud services, developer trust is becoming one of its main currencies. Microsoft is trying hard to regain that trust.
1, Because GitHub need to be careful about their decision, they will likely to give out more to convince people to keep using their product.
2, People now starting to trying tier 2 product from other companies, this is apparently a good thing for those companies. Also, you don't want to feed a monopoly.
Microsoft has a permanent interest to lock you in a box, paying tax. Open sourcing some products or whatever PR move is orthogonal to that, that's why they can do it.