But "extend" hasn't happened yet. There's no need to cry foul until it does, because until it does there's no evidence of anything nefarious going on. "Embrace" on its own is perfectly normal and acceptable behavior.

Vendor lock-in is an important concern regardless of who owns the platform you're being locked into.

The "extend" has already been done, by GitHub.

Git doesn't support issue tracking and pull requests.

The idea is that stuff like issues and PR comments (the added value a social coding site like GitHub provides) are the extend around pure git source management.

Fair point, but none of that is Microsoft's doing. Why are we only talking about this now?

Because Github wouldn't have been able to do the extinguish phase. Microsoft can, and will.

Pretty sure issues and PR comments came before the acquisition

So what do you call TypeScript !? They now bought the site where 99% of all free NodeJS packages are hosted. A few years ago NodeJS didn't even work properly on Windows, and was growing at exponential rate, taking market share from the Microsoft ecosystem. So what happened in the last few years ? Many developers now code JavaScript/NodeJS using TypeScript on VsCode. And their code is hosted on Github.

> But "extend" hasn't happened yet.

If we wait for it to happen by then it will be too late

So you're saying anytime a new technology gets embraced by anyone it's time to jump ship? That's ridiculous. Should we be abandoning email because Outlook exists?

Edit: Actually, I don't think the idea of "Embrace, Extend, Extinguish" even applies to buying out companies. The idea behind that phrase applies to technologies, not companies. You can't "extend" GitHub with proprietary tech, it was never an open source technology in the first place.

If Microsoft starts extending git with new proprietary features that only work with GitHub, _then_ it may be time to start being concerned. As of now though, I don't see how "Embrace, Extend, Extinguish" applies to this situation in the slightest.

GitHub is to git as Outlook is to e-mail and as Internet Explorer is to the web.

As for how EEE applies to this situation: The situation is consistent with an EEE strategy currently being in the "embrace" phase. It's also consistent with a "embrace, be nice, create win-win outcomes" strategy, but that is not usually Microsoft's modus operandi.

No need to get concerned. Just look at codeplex, it fully supports Git and Microsoft haven't touched that feature. :P

Unless they disable the APIs migrating to another platform would take a couple of days to hack something together. Disabling those APIs would also break a load of tools people already use for management so they would be shooting themselves in the foot.