Live data from Hacker News

We are moving the Roslyn code to GitHub

blogs.msdn.com

101–110 of 225 posts

Re: We are moving the Roslyn code to GitHub

#101
post #63

Earlier quoted context omitted.

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…

> 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. Except I'm not sure MS is still betting on Windows apps, and they're not making money off of .NET either. Of course, it's very prestigious to have your own dev tools/platform/language and all the big kids have them, but none of them are making money.

There are certainly more devs now than 20 years ago, and certainly more types of projects where the C#/.NET stack isn't appropriate, but I'm not sure your argument is valid beyond that.

Microsoft's also making plenty of money off .NET! Dev tools alone is a billion dollar business for them. The ecosystem around SharePoint alone (which sucks!) is larger than that of every tech on the HN homepage right now.

Spend five minutes in Visual Studio and it's clear that this is a massive ongoing engineering investment. I do an enormous amount of cross-platform development -- Mac, iOS, Linux, embedded systems -- and frankly everything else is caveman tools by comparison.

Re: We are moving the Roslyn code to GitHub

#102

Earlier quoted context omitted.

> Microsoft is about as marmite as you get in software (along with Oracle perhaps)... Sure, I have fond memories of the days when trendy developers would see me using a ThinkPad instead of a MacBook and ask, "Mike, when are you going to move away from the dark side?" Not so much any more. People I talk with seem reasonably impressed with the way Microsoft has been open sourcing .NET and other projects, making Visual…

I find this to be true of younger people who aren't aware of Microsoft's past and don't look at them with the sideways glance the rest of us do. In fact, I find it amazing how many younger people never even heard of their dark side and all the anti-trust movements on two continents.

I'm painfully aware of Microsoft's past, but it's not like Apple can (still) be considered the good guys either. It seems that some of the Apple crowd are learning this the hard way over the recent drama surrounding App Store policies.

My gut reaction to a ThinkPad will likely be better than to an MBP, simply because there's a higher chance it runs something other than OSX and Windows.

Re: We are moving the Roslyn code to GitHub

#103
post #27

Earlier quoted context omitted.

My only complaint about bitbucket is that I want to see the code easily, not click through heaps of buttons to do that.

In the settings of every repo you own in Bitbucket, there is a n option to set "Landing Page" to source code and it will open the root path of your repo when you hit the link.

Don't make me learn to use your site.

Re: We are moving the Roslyn code to GitHub

#104
post #93
post #63

Earlier quoted context omitted.

> 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. Except I'm not sure MS is still betting on Windows apps, and they're not making money off of .NET either. Of course, it's very prestigious to have your own dev tools/platform/language and all the big kids have them, but none of them are making money.

There are tons of enterprise apps that MS desperately wants to keep shackled to Windows. And of course, there's Windows Phone. MS without Windows and Office would die very quickly, they have to keep the platform alive.

Yet they keep pronouncing cloud first, mobile first. This kind of implies desktop last.

Re: We are moving the Roslyn code to GitHub

#105

BitBucket for private stuff/stuff I don't want showcasing. GitHub for open-source. Works perfectly fine for me and since they're both Git based there's no extra learning curves for either of them.

> BitBucket for private stuff/stuff I don't want showcasing. GitHub for open-source. I use them in the same way, but I can't help but feeling that I am taking advantage of Bitbucket and not giving anything in return, regardless of being good guy Bitbucket.

Get a monthly subscription. They limit you by number of team size, not number of repos.

Re: We are moving the Roslyn code to GitHub

#106
Are there any major public repository hosting services that provide good organizational tools for multiple repositories?

GitHub, as far as I have been able to determine, only supports a flat list sorted by last update.

This is annoying when a developer has a lot of repositories. I'll come across something useful in one of my areas of interest from a given developer, and then want to look at their other repositories to see if they have anything else in that area of interest. In a sane design, all of their repositories in that area would be organized under a folder, and this would be easy.

BitBucket seems to have the same limitation.

Re: We are moving the Roslyn code to GitHub

#107

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…

Also after them buying HockeyApp it wouldn't be the least bit surprising.

Re: We are moving the Roslyn code to GitHub

#108
post #70

Earlier quoted context omitted.

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…

I'd like to add that a lot of "cool kids" code in TypeScript, which is a Microsoft project.

I love TypeScript, and I wish it was more popular outside Microsoft, but it isn't.

Re: We are moving the Roslyn code to GitHub

#109
post #93

Earlier quoted context omitted.

There are tons of enterprise apps that MS desperately wants to keep shackled to Windows. And of course, there's Windows Phone. MS without Windows and Office would die very quickly, they have to keep the platform alive.

Yet they keep pronouncing cloud first, mobile first. This kind of implies desktop last.

Indeed. For Visual Studio and their development-server (Team Foundation Server, TFS for short) they have had a significant shift over the last few years.

TFS is available online under the name Visual Studio Online (a web only offering), with first class integration with Azure.

Development is done there first, and then later, every now and then, a on premises release is available that organizations can install on their server.

And the last updates have had significant features available only through the TFS web-portal. They were not made available via the Windows-components, like the intergrations for Visual Studio on the desktop. If you wanted the improved features you had to go the web-portal.

I'm starting to question whether Microsoft themselves see any value in developing a Windows-parallel to what is already a good enough web-solution. And if they can't be bothered, why should anyone else?

Re: We are moving the Roslyn code to GitHub

#110
Perhaps Microsoft wants to divest out of the git+online tools space? Github is the incumbent that they did not crack how to beat and it will be a bit more crowded with Amazon who seems to be also coming this year with CodeCommit. So far, Amazon strategy has been to suck all air from the room.
Post reply on HN