3 ms·

Typical Microsoft strategy: Embrace, extend and extinguish Soon the Platform will be renamed 'Microsost Visual Studio Github' or 'Microsoft team Github'. Then

Typical Microsoft strategy: Embrace, extend and extinguish Soon the Platform will be renamed 'Microsost Visual Studio Github' or 'Microsoft team Github'. Then 'microsoft Visual studio hub'. Then at somme point, Github will be inside Visual studio code online and not anymore the other way around!

zach_garwood 7y ago
Um, they own it, so why shouldn't they be allowed to put their name on it?
nojito 7y ago
What? This is just them creating a one stop shop for developers by expanding what GitHub offers. Nothing to do with EEE
- greatgib 7y ago
  Just think! You have Github. Git coming from linux, open source World, ... Also Github is notoriously the base of a lot of the ecosystem that is deprecating Microsoft solutions and environnement. All the website and js things of today are all developped by and for the unix world(linux, mac,..). In ms World, you were supposed to use proprietary closed heavy corporate solutions : c sharp, j2e, closed 'pro' server solutions. Si Github was the corner of all of that. Then they but it, suddenly there are a lot of features coming that bring it far from the scm job it was meant to. Now, it starts to be 'integrated' with ms tool ecosystem. How long before your Github accounts are merged, shared, replace with a Microsoft account? They will tell you that it makes sense and is needed because vscode needs to be interconnected with ms team and co...
  - nojito 7y ago
    You seem to have closed your eyes for the MS of the past 10 years. The 90s are over.
- greatgib 7y ago
  And btw, don't forget the past. They had 'team fondation server' (that is now azure devons server'), that was shitty and git and Github were terrible competitors.: https://wilsonmar.github.io/tfs-vs-github/ https://wilsonmar.github.io/tfs-vs-github/ And all of tfs was volontarely deeply intricated with Visual studio useless things.
screye 7y ago
Just goes to show hard a reputation can be to let go of. Different people, different leadership, different strategy and an entirely innocuous product offering. But people still find a way to relate it to EEE.
- cachestash 7y ago
  Its legacy thinking.
blackoil 7y ago
Github was since forever a proprietary product, so EEE doesn't apply here. This is equivalent to buying a closed email client and integrating it with MS Office.

zach_garwood 7y ago

Um, they own it, so why shouldn't they be allowed to put their name on it?

nojito 7y ago

What? This is just them creating a one stop shop for developers by expanding what GitHub offers. Nothing to do with EEE

greatgib 7y ago
Just think! You have Github. Git coming from linux, open source World, ... Also Github is notoriously the base of a lot of the ecosystem that is deprecating Microsoft solutions and environnement. All the website and js things of today are all developped by and for the unix world(linux, mac,..). In ms World, you were supposed to use proprietary closed heavy corporate solutions : c sharp, j2e, closed 'pro' server solutions. Si Github was the corner of all of that. Then they but it, suddenly there are a lot of features coming that bring it far from the scm job it was meant to. Now, it starts to be 'integrated' with ms tool ecosystem. How long before your Github accounts are merged, shared, replace with a Microsoft account? They will tell you that it makes sense and is needed because vscode needs to be interconnected with ms team and co...
- nojito 7y ago
  You seem to have closed your eyes for the MS of the past 10 years. The 90s are over.
greatgib 7y ago
And btw, don't forget the past. They had 'team fondation server' (that is now azure devons server'), that was shitty and git and Github were terrible competitors.: https://wilsonmar.github.io/tfs-vs-github/ https://wilsonmar.github.io/tfs-vs-github/ And all of tfs was volontarely deeply intricated with Visual studio useless things.

screye 7y ago

Just goes to show hard a reputation can be to let go of. Different people, different leadership, different strategy and an entirely innocuous product offering. But people still find a way to relate it to EEE.

cachestash 7y ago
Its legacy thinking.

blackoil 7y ago

Github was since forever a proprietary product, so EEE doesn't apply here. This is equivalent to buying a closed email client and integrating it with MS Office.