Live data from Hacker News

We are moving the Roslyn code to GitHub

blogs.msdn.com

51–60 of 225 posts

Re: We are moving the Roslyn code to GitHub

#51
post #32

Pretty cool! Are all these happening because Satya Nadella is trying to steer MS in new direction?

Maybe? But I think its more just a natural evolution. Scott Hanselman has been making noise regarding open source for years [1]. I'm not saying Scott is responsible, just that many people have been suggesting it for a long long time. I saw a job today asking for TFS skills. THAT is a dying product... [1] http://www.hanselman.com/blog/ExampleHowToContributeAPatchTo...

You missed the part that TFS is much more than just source control and since TFS 2012 also supports Git.

Re: We are moving the Roslyn code to GitHub

#52
post #32

Pretty cool! Are all these happening because Satya Nadella is trying to steer MS in new direction?

Maybe? But I think its more just a natural evolution. Scott Hanselman has been making noise regarding open source for years [1]. I'm not saying Scott is responsible, just that many people have been suggesting it for a long long time. I saw a job today asking for TFS skills. THAT is a dying product... [1] http://www.hanselman.com/blog/ExampleHowToContributeAPatchTo...

You missed the part that TFS is much more than just source control and since TFS 2012 also supports Git.

Re: We are moving the Roslyn code to GitHub

#55
post #40

Earlier quoted context omitted.

Microsoft or otherwise, I don't think the idea that GitHub is going to be run like a public utility forever is a smart bet.

It's reasonably easy to pick up your repo and leave. How easy is it to pick up your bugs and leave?

Reasonably easy: https://github.com/gitlabhq/gitlab-recipes/blob/master/impor...

Re: We are moving the Roslyn code to GitHub

#56
post #40

Earlier quoted context omitted.

Microsoft or otherwise, I don't think the idea that GitHub is going to be run like a public utility forever is a smart bet.

It's reasonably easy to pick up your repo and leave. How easy is it to pick up your bugs and leave?

Pretty easy;

https://developer.github.com/v3/issues/#list-issues-for-a-re...

Re: We are moving the Roslyn code to GitHub

#57

> HOW: This will be a simple switch – turn off CodePlex, turn on GitHub. You’ll be able to see our check-ins on GitHub that same day. It's probably a safe bet that CodePlex's days are numbered. Which is kind of a shame. It was definitely heavily lacking but I can't help but think that some more competition in the space would be a good thing.

I definitely like how CodePlex has dedicated tabs for documentation, as well as discussion and issues. It seems like every repo I come across on github is often just a dump of files with very little in the way of documentation. My guess is that because CodePlex makes documentation prominent, it incentivises its use while the opposite is true for github.

Re: We are moving the Roslyn code to GitHub

#58
post #54

What were they previously using before the switch to git? Mercurial?

git != Github. Github just hosts git repositories. You can use git and not host on Github. They were using git, but hosting the repository on CodePlex.

>We are moving our code to GitHub as well as switching to use git internally

But they were using a different tool internally.

Re: We are moving the Roslyn code to GitHub

#59
post #36

This is getting terrifyingly close to my prediction that Microsoft should/would/will buy GitHub. When I first started predicting this two or so years ago, it was mainly for its comedic value (it always got laughs, followed by "yeah, they should!" followed by nervous laughter followed by "wait, do you think they would actually do that?!"), but after the open sourcing of .NET I honestly think anything is possible. Espe…

What does MS gain? Is online source code storage really going to be a million or billion dollar business for them? It seems like it's just a race to the bottom with costs, just like Dropbox, Box, etc. etc.

pjmlp has it right, but I'll add some further clarifications.

One of the most important aspects of Microsoft's success is network effect. People use Windows and Office because other people use Windows and Office.

But network effect also works on the development/platform side. Devs write apps in the technologies they know and are comfortable with, and those tend to be the technologies they've used for personal or work projects. Today, far fewer of the top tier (even the top 50% really) of developers are using Microsoft technologies, or are even familiar with them. The "cool kids" code in Ruby or Python or Scala or Golang, or mobile specific languages. If they want to get things done to pay the bills they might fall back on java or PHP. But the idea of using C#, .NET, or coding Windows Apps? Far fewer devs under 30 are doing that than they were 10 or 20 years ago.

With fewer devs coding on your platform that means there will be fewer apps, especially the most desired ones, and eventually that will impact the user base as well and weaken the entire business. The era where nobody cares whether a computer runs windows is on the horizon today, even though it may be many years away. If you look at the big apps and systems from the last 5 years you see that a lot of them are either web based or mobile (specifically android/iOS as well).

Microsoft used to understand this and it was a major reason why they invested in Visual Studio for all those years when it was unprofitable. But they've had a period of unrivaled market dominance which has only recently been challenged, so they lost their way for a while.

Catering to devs is how you maintain market relevancy with your platform, which is something Microsoft desperately needs.

Additionally, improving the relationship with the dev community and attracting more devs to your platform makes hiring easier (especially hiring talented folks). It's almost impossible to objectively quantify the benefit of that but it's an enormous factor. Microsoft has been bleeding talent for years and has been starved of a lot of talent for a long time because they were perceived as being old and boring and requiring a completely different set of proficiencies to work there. If Microsoft wanted to they could turn that around and start paving a road back to relevancy in the dev community again.

Re: We are moving the Roslyn code to GitHub

#60

This is getting terrifyingly close to my prediction that Microsoft should/would/will buy GitHub. When I first started predicting this two or so years ago, it was mainly for its comedic value (it always got laughs, followed by "yeah, they should!" followed by nervous laughter followed by "wait, do you think they would actually do that?!"), but after the open sourcing of .NET I honestly think anything is possible. Espe…

It'd be a smart buy for a large software company, hedging their bets on moving into open source. I don't think it's out of the realms of possibility either.

It would be a horrible buy for any polarising brand. Microsoft is about as marmite as you get in software (along with Oracle perhaps) regardless of their recent attitude to being open. We have to be past the point where anyone with purchasibg power believes you can aquire credibility.
Post reply on HN