4 ms·

Embrace and Extend, anyone? (I don't expect anything nefarious, Microsoft doesn't have the power these days to make GVFS the default git client for 90% of deve

by ploxiln 10y ago

Embrace and Extend, anyone? (I don't expect anything nefarious, Microsoft doesn't have the power these days to make GVFS the default git client for 90% of developers, it's just amusingly MS style...)

Ezhik 10y ago
Can we just get a bot that posts EEE on every article about Microsoft? Seriously, every damn time.
- ploxiln 10y ago
  It's the first time I've posted it, and I think it's more appropriate for this story than others in recent memory. I'm also pretty sure I haven't seen it on the many VSCode stories (and I have "showdead" enabled).
  - sdesol 10y ago
    I've been studying the SCM war with great interest and I like to think of myself, as an impartial observer, from a Git hosting point of view. Since my product is built around Git and not Git hosting, it doesn't really matter to me, who (GitHub, GitLab, Microsoft, etc.) wins the Git hosting war. The only thing that matters for me, is Git gaining greater mind share in Enterprise. And I think Microsoft's flurry of activity in the Git hosting world, is not them trying to embrace it, so they can extinguish it. But rather, it's them trying to ensure they don't lose relevance. In the past, when we had SCM diversity (ClearCase, Perforce, Subversion, Git, etc.), companies who managed the SCM technology, controlled the software development life cycle. However, with Git, where there is no owner, you can't control the software development life cycle, like you use to. Microsoft embracing Git like they are, is just them flexing their vast technical and financial resources, so they can get people to migrate to their ecosystem. They know they can't extinguish Git, and since they can't dictate how Git evolves, their next best option is to make working with Git better in their world.
deelowe 10y ago
2002 was over 10 years ago. This meme has run it's course. It's pretty clear MS has a different strategy these days, which makes sense. The market is totally different.
- harry8 10y ago
  2016 was last year. There is no point complaining than an earned and deserved reputation is earned and deserved.
  - harry8 10y ago
    Sorry, I should point out it is not a "meme" whatever the hell that is. It was (and we have no evidence whether it still is) Microsoft policy. As found by the US DOJ. They've probably stopped using the term internally, which I believe because I don't think MS execs are stupid. https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish Not a meme. An earned and deserved reputation. I'm sure Microsoft don't like their reputation and that's kind of the point.

by ploxiln 10y ago

Embrace and Extend, anyone? (I don't expect anything nefarious, Microsoft doesn't have the power these days to make GVFS the default git client for 90% of developers, it's just amusingly MS style...)

Ezhik 10y ago

Can we just get a bot that posts EEE on every article about Microsoft? Seriously, every damn time.

ploxiln 10y ago
It's the first time I've posted it, and I think it's more appropriate for this story than others in recent memory. I'm also pretty sure I haven't seen it on the many VSCode stories (and I have "showdead" enabled).
- sdesol 10y ago
  I've been studying the SCM war with great interest and I like to think of myself, as an impartial observer, from a Git hosting point of view. Since my product is built around Git and not Git hosting, it doesn't really matter to me, who (GitHub, GitLab, Microsoft, etc.) wins the Git hosting war. The only thing that matters for me, is Git gaining greater mind share in Enterprise. And I think Microsoft's flurry of activity in the Git hosting world, is not them trying to embrace it, so they can extinguish it. But rather, it's them trying to ensure they don't lose relevance. In the past, when we had SCM diversity (ClearCase, Perforce, Subversion, Git, etc.), companies who managed the SCM technology, controlled the software development life cycle. However, with Git, where there is no owner, you can't control the software development life cycle, like you use to. Microsoft embracing Git like they are, is just them flexing their vast technical and financial resources, so they can get people to migrate to their ecosystem. They know they can't extinguish Git, and since they can't dictate how Git evolves, their next best option is to make working with Git better in their world.

deelowe 10y ago

2002 was over 10 years ago. This meme has run it's course. It's pretty clear MS has a different strategy these days, which makes sense. The market is totally different.

harry8 10y ago
2016 was last year. There is no point complaining than an earned and deserved reputation is earned and deserved.
- harry8 10y ago
  Sorry, I should point out it is not a "meme" whatever the hell that is. It was (and we have no evidence whether it still is) Microsoft policy. As found by the US DOJ. They've probably stopped using the term internally, which I believe because I don't think MS execs are stupid. https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish Not a meme. An earned and deserved reputation. I'm sure Microsoft don't like their reputation and that's kind of the point.