News for hackers. Stuff that matters.
Re:We are moving the Roslyn code to GitHub by bcantrill on Sunday January 11, 2015 @04:08AM (#8869507)
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. Especially because the counter to MSFT buying GitHub was always "but... CodePlex!", and here they are explicitly moving a high-profile project from CodePlex to GitHub. Scary!
Re:We are moving the Roslyn code to GitHub by brudgers on Sunday January 11, 2015 @05:22AM (#8869601)
I've been listening my way through the archive of Scott Hanselman's hanselminutes podcasts. Microsoft has been striving to be on the right side of history in regard to open source for five or six years. It's all out in the open.

Moving to Github is simply developer friendly.

Don't misunderstand me. Microsoft's products compete with open source software in the marketplace for developer mindshare and I am not suggesting that this is not a business decision. Being on Github helps the company iterate quickly rather than on the multiyear cycles that were standard when software came in a box.

Will Microsoft buy Github?

Only if Github is selling.

And there was value for Microsoft. There isn't amazing technology, there. There's a huge liability for litigation hosting just anyone's content that comes with Microsoft size pockets, and Git, being distributed would allow an angry community to set up their own Son of Github if Microsoft took control and acted improperly.

Incidentally, WiX has been on SourceForge since 2006. There's been nary a rumor of a deal there.

Re:We are moving the Roslyn code to GitHub by a3n on Sunday January 11, 2015 @11:30AM (#8870344)
"Only if Github is selling."

Everyone is selling, for the right number of billions.

"We are excited about this new stage, because we are better positioned to ..."

Re:We are moving the Roslyn code to GitHub by mbesto on Sunday January 11, 2015 @12:46PM (#8870558)
a16z is their lead investor. Which presumptuously means there is definitely a selling price and Microsoft definitely has cash.
Re:We are moving the Roslyn code to GitHub by brudgers on Sunday January 11, 2015 @04:16PM (#8871344)
A number of big players have the cash...Apple, Google, Oracle. So do sovereign investment funds and Berkshire-Hathaway. Other than FUD, there's nothing pointing to Microsoft and Google makes far more extensive use of Github:

https://github.com/google

Re:We are moving the Roslyn code to GitHub by tedunangst on Sunday January 11, 2015 @07:53PM (#8871986)
I like the idea that speculation Microsoft may buy github can only be FUD and not simply speculation.
Re:We are moving the Roslyn code to GitHub by finenad on Sunday January 11, 2015 @08:29AM (#8869901)
Even though Microsoft have embraced open source, they are not happy about the GPL license, and have actively replaced GPL code in their previous takeovers.
Re:We are moving the Roslyn code to GitHub by brudgers on Sunday January 11, 2015 @08:45AM (#8869938)
[IANAL]

My impression is that GPL (or another copyleft style licence) would create incompatibilities with the business models of many of their customers. Taking contributions would also be problematic since Microsoft may wish to dogfood their opensource for proprietary products.

For better or worse many of their products incorporate licensed technology from other companies under terms incompatible with GPL. So GPL's strong terms don't seem a viable and reasoned alternative.

GPL might be seen as a strong option for companies whose business is built around dual licensing their technology and when all that technology was built in house or licenced under different less stringent terms.

Re:We are moving the Roslyn code to GitHub by bunderbunder on Sunday January 11, 2015 @10:48AM (#8870228)
This. GPL is just really really hard to work around if you're selling non-SAAS products. In general, it's not something you try to do if you have any alternative. And nowadays, you almost always have an alternative. Increasingly often it's a more capable, more actively maintained, and better supported option that comes with the added bonus of not needing to take the time to get special approval from your legal department.
Re:We are moving the Roslyn code to GitHub by woodman on Sunday January 11, 2015 @03:54PM (#8871262)
> if you're selling non-SAAS products

Pretty funny, considering how much RMS dislikes SAAS.

Re:We are moving the Roslyn code to GitHub by s-phi-nl on Sunday January 11, 2015 @09:32PM (#8872226)
I do not know, but I suspect this is exactly why RMS dislikes SAAS: because it can technically obey a license without having to give users the freedoms he designed the GPL to give.
Re:We are moving the Roslyn code to GitHub by bunderbunder on Sunday January 11, 2015 @09:55PM (#8872292)
It's deeper than that. By its very nature, SAAS precludes every single one of the freedoms that the GPL is designed to give.

The GPL isn't really about sharing source code; that's just a means to an end. The GPL is about being able to exercise complete control over - and having complete knowledge of - all the software that you use. To an approximation, SAAS is about the opposite of that.

Re:We are moving the Roslyn code to GitHub by tiernano on Sunday January 11, 2015 @04:33PM (#8871412)
Microsoft might not be happy with the GPL itself, but given they are working on LibGit, and not all of GitHub (or any?) of their main software they "sell" (github enterprise, their client apps like GitHub for Windows and OSX) are open source, Microsoft would probably have no issues with the GPL. It would also be interesting if MS did buy GitHub. Wasent one of the GitHub founders an employee of a company who was bought by Microsoft and he either dident move over or left after a minimum time?
Re:We are moving the Roslyn code to GitHub by nbevans on Sunday January 11, 2015 @11:56PM (#8872576)
I think most people have issue with GPL to be honest. So they aren't alone there.
Re:We are moving the Roslyn code to GitHub by jenscow on Sunday January 11, 2015 @05:06PM (#8871526)
> It's all out in the open.

Really? So they release the source to a few of their developer frameworks and tools, and they're now "all open"?

Don't get me wrong, as a long time C# developer I do appreciate the gesture and I'm especially happy that they're working their "not invented here" mentality, but with simply providing us with the source code that we already have anyway (via ilspy), all of this just seems over-inflated to me.

Let me compile Visual Studio, and I'll be their biggest cheerleader; or IIS, IE... and I'll promise to stop dressing as one.

On buying Github, though? That could be the final 'E' of their strategy.

Re:We are moving the Roslyn code to GitHub by sillysaurus3 on Sunday January 11, 2015 @07:56PM (#8871994)
Completely agreed. Once Microsoft releases the VS source code, I'll be completely sold on the idea that it's reformed. Until then, this seems like very effective developer relations management.
Re:We are moving the Roslyn code to GitHub by nbevans on Sunday January 11, 2015 @11:59PM (#8872583)
Why the VS source code? It would be almost entirely useless to anybody as there is 2 decades of legacy in that code base and MS has massive teams just trying to keep it all together. Only open source things that are WORTH open sourcing i.e. where you want active contributors.
Re:We are moving the Roslyn code to GitHub by jenscow on Monday January 12, 2015 @03:58AM (#8872983)
Why VS? So when things are removed, "we" can continue to maintain them. Sure, that provides no benefit for Microsoft but it does to its customers. It will also show the are serious about being "all open", rather than a few self-satisfying token gestures.
Re:We are moving the Roslyn code to GitHub by sillysaurus3 on Monday January 12, 2015 @03:49AM (#8872965)
If I could compile VS myself, on my own box, that would be massive in ways that are hard to articulate. I wouldn't be contributing to VS. I'd be modifying VS for my own purposes, which is what open source is about.
Re:We are moving the Roslyn code to GitHub by bunderbunder on Sunday January 11, 2015 @09:16PM (#8872183)
This isn't big because Microsoft has stared sharing source. The source to the .NET framework has been available _without_ ILSpy for years now.

This is big because Microsoft is truly embracing an open source development model. They've opened most of the .NET platform up to the whole shebang - pull requests, copying code into other projects, forking, all that good stuff.

Re:We are moving the Roslyn code to GitHub by jenscow on Monday January 12, 2015 @04:05AM (#8872993)
So the big deal is that we're now allowed to modify the code of a few libraries?

Fair enough.

Re:We are moving the Roslyn code to GitHub by wernercd on Monday January 12, 2015 @09:39AM (#8874048)
MS is closed source? People Bitch.

MS moves to open source parts? People Bitch.

Can't win...

Re:We are moving the Roslyn code to GitHub by brudgers on Monday January 12, 2015 @02:56PM (#8876031)
My point is that the changes in Microsoft's attitude toward open source have occurred in the open.

It is a response to its parent comment which strongly suggests the attitude reflects a sudden and nefarious change in Microsoft's behaviour.

Re:We are moving the Roslyn code to GitHub by bobajeff on Monday January 12, 2015 @10:40AM (#8874425)
Yeah until they open source something else important to their platform (e.g. the NT kernel, DirectX, Trident/Chakra) saying they've fully embraced open source is a little premature.
Re:We are moving the Roslyn code to GitHub by grandalf on Sunday January 11, 2015 @07:32AM (#8869802)
It's great to see MS making smart choices!
Re:We are moving the Roslyn code to GitHub by SwellJoe on Sunday January 11, 2015 @05:05AM (#8869581)
They'd have to bid against Google, by this logic, since Go also moved to Github recently.
Re:We are moving the Roslyn code to GitHub by tankenmate on Sunday January 11, 2015 @07:43AM (#8869822)
Sorry I didn't mean to vote you down, my baby daughter hit my hand while I was holding the mouse. I can't seem to find a way change my vote; is there one?
Re:We are moving the Roslyn code to GitHub by sunir on Sunday January 11, 2015 @08:24AM (#8869888)
Teach your daughter to hack so she can up and down vote on her own Hacker News account.
Re:We are moving the Roslyn code to GitHub by bborud on Sunday January 11, 2015 @07:57AM (#8869845)
I voted him up for you. :-)
Re:We are moving the Roslyn code to GitHub by jrs235 on Sunday January 11, 2015 @02:16PM (#8870904)
Wait wait wait! Why would Microsoft, or any company, increase the value of a company before buying it (thus increasing the amount they have to payout to existing shareholders)? Wouldn't you think Microsoft or some other company would buy first, then make the company worth more? For example, let's say Chevy is [seriously] thinking about buying [BatteryCompany]. Would Chevy put in an order for millions of dollars worth of batteries and then buy, requiring Chevy to pay more to existing shareholders? Or would Chevy try buying the company then placing the orders to its subsidiary?
Re:We are moving the Roslyn code to GitHub by mschwaig on Thursday January 22, 2015 @12:22PM (#8930337)
I think this is more like Chevy stopping to produce all the parts on their own and instead starting to use trusted parts provided by third parties which the rest of the industry already agrees on using. Buying the manufacturer of one such part really makes less sense if your company follows a completely different production philosophy.
Re:We are moving the Roslyn code to GitHub by tdicola on Sunday January 11, 2015 @05:13AM (#8869588)
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.
Re:We are moving the Roslyn code to GitHub by rbanffy on Sunday January 11, 2015 @07:00AM (#8869753)
> What does MS gain?

Image.

Microsoft's message has been it's a one-stop-shop for your IT needs, as opposed to the general open-source ecosystem where everything has a different vendor (if at all). This, and the difficulty of moving to other platforms/vendors/tools was the core of its vendor lock-in power. In the 80's and most of the 90's, I went full Microsoft, from runtime to database to developer tools, because everything worked so well together.

Microsoft has been changing, of course, but if not even Microsoft uses Microsoft products, why should companies use them?

With this, again, we see the tacit admission a product or service built on top of free software is somehow better than the technologies Microsoft sells.

Re:We are moving the Roslyn code to GitHub by hueving on Sunday January 11, 2015 @09:55AM (#8870111)
You can't just buy image. If anything it would just dilute the image of github. It's like the rich kid trying to make friends by buying the basketball court.
Re:We are moving the Roslyn code to GitHub by coldtea on Sunday January 11, 2015 @11:16AM (#8870296)
>It's like the rich kid trying to make friends by buying the basketball court.

You'd be surprised how effective that can be...

Re:We are moving the Roslyn code to GitHub by VLM on Sunday January 11, 2015 @04:47PM (#8871464)
And yet, they bought Minecraft, which seems to be exactly that strategy.
Re:We are moving the Roslyn code to GitHub by untog on Monday January 12, 2015 @01:11AM (#8872708)
I don't think MS bought Minecraft for image. I think they bought it because it's very successful and has a chance to make a ton of money.
Re:We are moving the Roslyn code to GitHub by wernercd on Monday January 12, 2015 @09:42AM (#8874070)
Why can't it be both? Mind-share AND money.
Re:We are moving the Roslyn code to GitHub by hueving on Sunday January 11, 2015 @10:56PM (#8872430)
Well I would argue that it didn't work. I didn't even know that Microsoft was involved with Minecraft until you mentioned it.
Re:We are moving the Roslyn code to GitHub by rbanffy on Sunday January 11, 2015 @10:18AM (#8870158)
We know they can't but interesting things happen when you are both desperate and rich.
Re:We are moving the Roslyn code to GitHub by InclinedPlane on Sunday January 11, 2015 @06:11AM (#8869675)
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 by rjbwork on Sunday January 11, 2015 @07:31AM (#8869799)
Under-30 dev here. Been programming in C# for the past 3.5 years now, and loving every minute of it. I find VS and the associated tools be a far more productive and enjoyable experience than the Linux/Unix toolchains I was forced to use in undergrad, and C# to be a completely amazing language. The two warts, for me, are MSBuild (powerful, but obtuse at times, but still better than make) and PowerShell (again, powerful, but obtuse at times).

I also really like how .NET has first-rate libraries for the Azure ecosystem. It really makes doing some very technically difficult/interesting things easy on Azure.

As for others, I work with 2 developers who have made the jump from Java/JavaScript to working in C#/.NET because it is just a plain-old better experience.

As for relevancy and devs, C# is huge in enterprise, as I'm sure you know. I don't think they're really fighting to maintain relevancy there, and I would suggest that since the advent of MVC and Azure, they are growing in relevancy in the SaaS space.

Re:We are moving the Roslyn code to GitHub by pmelendez on Sunday January 11, 2015 @08:18AM (#8869876)
>"Under-30 dev here. Been programming in C# for the past 3.5 years now, and loving every minute of it."

Mid 30's here. I work mostly on C++ but I have to jump into C# code once in a while. I agree that C# is a very productive language and I love how it never gets in your way ("Do you say you don't want to use a common interface for your generics? Use dynamic!").

My only "complaint" is that C# is so indulgent that it gets boring at times, which might actually be a feature.

Re:We are moving the Roslyn code to GitHub by to3m on Sunday January 11, 2015 @11:16AM (#8870295)
C# is oft underrated, in my view. It's very quick to code in, is part of a large (if Windows-centric) ecosystem, and has been generally fairly tastefully designed. Compared to other languages you might compare it to, its designers aren't afraid to be a bit avant garde at times (unlike Java), it's got static typing (unlike Python), it's got garbage collection (unlike C), and... well, I know Go programmers hate it when people drop the G-bomb. But it's got that too. Unlike Go.
Re:We are moving the Roslyn code to GitHub by pmelendez on Sunday January 11, 2015 @02:08PM (#8870873)
G-bomb?
Re:We are moving the Roslyn code to GitHub by andrewchoi on Sunday January 11, 2015 @02:17PM (#8870907)
I assume he means generics.
Re:We are moving the Roslyn code to GitHub by to3m on Sunday January 11, 2015 @07:41PM (#8871952)
Maybe... :)

I was a little circumspect because the usual response to any suggestion that a lack of generics might be some kind of problem is - generally - not positive.

But my point is merely that C# has this thing, and Go doesn't. If I knew enough about Go to say instead that it lacks something else that C# has, I'd have done that...

Re:We are moving the Roslyn code to GitHub by hueving on Sunday January 11, 2015 @10:02AM (#8870127)
>It really makes doing some very technically difficult/interesting things easy on Azure.

Doesn't that just mean Azure has horrible APIs that are impossible to work with without the 'magic tooling'?

Re:We are moving the Roslyn code to GitHub by tracker1 on Sunday January 11, 2015 @04:25PM (#8871379)
I've been using some Azure bits with node.js without much issue... I'd say that C# is probably my second favorite language, and that I really like JS as my first. Which really doesn't fall in line with a lot of people, but that's where I stand... I actually like each for their differences.

Part of my own reasons for moving away from C# and much more into the node ecosystem has been in terms of licensing and avoiding lock in. Now that MS is going a much more open route, I'm willing to actually consider some pieces in that direction again.

VS can be very nice to work with, my single largest issue has been how systems have been designed with it, far above and beyond issues with the underlying platforms or the language. The tooling is very nice. However my experiences with "Enterprise" projects leaves a bitter taste in my mouth.

More often than not, I've seen "Enterprise" (quotes intentional) projects that seem to add complexity for its' own sake. Writing code that is unit tested in Java or C# are just plain painful compared to say JS/node. I find that comes down to differences between a static platform and a dynamic one though.

I think MS is rightly pushing for greater Azure deployment of server-side applications. The desktop is dying for most people, and mobile is not going away. By opening the tools, and providing better integration, they allow for a transparent deployment to Azure which is a rented platform which will receive more consistent revenue. It's simply good business.

Re:We are moving the Roslyn code to GitHub by rjbwork on Sunday January 11, 2015 @03:33PM (#8871184)
Maybe, TBH I've never tried using their services in any other way.
Re:We are moving the Roslyn code to GitHub by pron on Sunday January 11, 2015 @06:24AM (#8869699)
> 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.

Re:We are moving the Roslyn code to GitHub by tacos on Sunday January 11, 2015 @09:11AM (#8870006)
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 by Retra on Sunday January 11, 2015 @03:06PM (#8871078)
Microsoft's development tools are (therefore) expensive, so unless you're getting paid to use them, it's harder to invest yourself in them.
Re:We are moving the Roslyn code to GitHub by Encosia on Sunday January 11, 2015 @04:14PM (#8871337)
There's been a free version of each Visual Studio release for about ten years.
Re:We are moving the Roslyn code to GitHub by cmdkeen on Sunday January 11, 2015 @05:54PM (#8871664)
More than that the Community Edition keeps getting more fully featured. To the point where for the average indie developer there isn't that much difference, especially compared to the intro paid edition. Plus with Bizspark you get 3 Ultimate licences.
Re:We are moving the Roslyn code to GitHub by Retra on Sunday January 11, 2015 @04:24PM (#8871377)
And it'll run on my Linux machine, presumably?
Re:We are moving the Roslyn code to GitHub by Encosia on Sunday January 11, 2015 @05:19PM (#8871558)
About as well as Xcode runs on my Windows machine, but there are always VMs.

(I wasn't who downvoted you, BTW)

Re:We are moving the Roslyn code to GitHub by Retra on Sunday January 11, 2015 @06:49PM (#8871811)
Well, as a fairly broke student who doesn't own any Windows computers (and who's plenty tired of Java), I've found that getting into C# is unnecessarily unpleasant. It doesn't help that everybody's advice seems to be "get Visual Studio."

I'm sure it's great, and if I put more effort into it I might get something to work. But it is a real barrier: Why should I jump to C# if it isn't actually any more convenient?

Re:We are moving the Roslyn code to GitHub by Encosia on Sunday January 11, 2015 @07:32PM (#8871930)
As a student, you should look into this program: https://www.dreamspark.com/

There are some great cross-platform developments in the pipeline that should allow you to have a native Linux experience approaching VS the future, but you really should use VS if you want the best experience with C#/.NET today. DreamSpark will give you access to free licenses of Windows and VS (and other Microsoft software), that you can install in a free VM host like VirtualBox, so don't let the perceived costs of using VS deter you.

I can't remember if DreamSpark comes with any Azure credits. If it does come with the $150/mo credit that most MSDN subscriptions do, you can use that to run a Windows/VS VM in Azure and just RDP to that. They have templates prebuilt so you can spin up a new VM with Windows and Visual Studio already installed with one click. That's a great way to get up and running very quickly: http://blogs.msdn.com/b/visualstudioalm/archive/2014/06/04/v...

My email's in my profile here. Feel free to get in touch if I can help with anything.

Re:We are moving the Roslyn code to GitHub by Retra on Sunday January 11, 2015 @08:59PM (#8872152)
I will look into that, thanks.
Re:We are moving the Roslyn code to GitHub by pron on Monday January 12, 2015 @05:54PM (#8876995)
If you want C# for the JVM, take a look at Kotlin: http://kotlin-lang.org/
Re:We are moving the Roslyn code to GitHub by shanselman on Tuesday January 20, 2015 @04:52AM (#8916174)
Re:We are moving the Roslyn code to GitHub by locusm on Sunday January 11, 2015 @06:49PM (#8871810)
Plus you can be locked out of VS if you go away for a weekend and haven't signed into the IDE in a while. Happened to me twice last year. Let me repeat that - they force you to login to their tools (that Ive paid for) and if you don't the IDE is rendered unusable. Fuck the guy in the VS team that OK'ed that feature.

But it was a blessing in disguise really as it made me look into other pastures like Node & Laravel.

Re:We are moving the Roslyn code to GitHub by locusm on Monday January 12, 2015 @10:41AM (#8874432)
This is in reference to the partner version of VS.
Re:We are moving the Roslyn code to GitHub by jabits on Monday January 12, 2015 @10:32AM (#8874351)
This is bs.
Re:We are moving the Roslyn code to GitHub by toyg on Sunday January 11, 2015 @08:35AM (#8869914)
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.
Re:We are moving the Roslyn code to GitHub by tonyedgecombe on Sunday January 11, 2015 @09:29AM (#8870044)
Yet they keep pronouncing cloud first, mobile first. This kind of implies desktop last.
Re:We are moving the Roslyn code to GitHub by josteink on Sunday January 11, 2015 @09:52AM (#8870105)
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 by nawitus on Sunday January 11, 2015 @07:02AM (#8869756)
I'd like to add that a lot of "cool kids" code in TypeScript, which is a Microsoft project.
Re:We are moving the Roslyn code to GitHub by nailer on Sunday January 11, 2015 @09:42AM (#8870076)
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 by nawitus on Sunday January 11, 2015 @12:05PM (#8870439)
I'd say it's relatively popular. It's also growing quite quickly:

http://blog.javascripting.com/2014/07/28/fastest-growing-new...

Re:We are moving the Roslyn code to GitHub by nailer on Sunday January 11, 2015 @01:05PM (#8870619)
That's good to hear (and better data than my anecdotal evidence - I suspect I may live in a bubble of conference going JS devotees) - I stand corrected.
Re:We are moving the Roslyn code to GitHub by cmdrfred on Sunday January 11, 2015 @11:11AM (#8870284)
"My father taught me many things here — he taught me in this room. He taught me — keep your friends close but your enemies closer." - Michael Corleone
Re:We are moving the Roslyn code to GitHub by pjmlp on Sunday January 11, 2015 @05:46AM (#8869640)
Hipster value. All the cool kids are now using Github.
Re:We are moving the Roslyn code to GitHub by josteink on Sunday January 11, 2015 @06:32AM (#8869710)
In a non-sarcastic world it's called "community" and it increases the chance of getting collaborators contributing to your project.

You know, the point of open-source being that everyone should be able to contribute and all that.

Re:We are moving the Roslyn code to GitHub by sfk on Sunday January 11, 2015 @07:27AM (#8869789)
In a naive world it's called community. These days open source is a vehicle for multinationals to get suckers to write and test their software for free.

Microsoft has caught on to that, hence the move.

Re:We are moving the Roslyn code to GitHub by josteink on Monday January 12, 2015 @01:55AM (#8872782)
> These days open source is a vehicle for multinationals to get suckers to write and test their software for free.

Lets for arguments sake accept your statement as fact. If that is a fact, is that inherently a bad thing?

If I use a piece of software, open-source or not, will I or will I not benefit from that software somehow obtaining better test-coverage? Ofcourse I will.

If that software is important to me, being able to contribute with tests or other "boring" or "light" material means that the core team can focus on further development. And I honestly don't have a problem with that.

Re:We are moving the Roslyn code to GitHub by sfk on Sunday January 11, 2015 @10:19AM (#8870161)
The downvoters should educate themselves:

http://www.joelonsoftware.com/articles/StrategyLetterV.html

Re:We are moving the Roslyn code to GitHub by higherpurpose on Sunday January 11, 2015 @08:36AM (#8869918)
Microsoft does lots of money-losing acquires. Think Skype. They'll recover their money in 20 years (unless they account the contracts they're getting from the government for giving them Skype access as amortization).
Re:We are moving the Roslyn code to GitHub by hueving on Sunday January 11, 2015 @09:56AM (#8870117)
You don't get a contract for being forced to comply with a secret court order for information.
Re:We are moving the Roslyn code to GitHub by DonHopkins on Sunday January 11, 2015 @05:58PM (#8871673)
Of course you are correct. The NSA never gives money to companies to weaken security. That would be unethical and un-American.

http://www.reuters.com/article/2013/12/20/us-usa-security-rs...

And it's also true that James Clapper didn't lie, he simply misspoke.

http://www.cbsnews.com/news/james-clapper-says-he-misspoke-d...

"It has been very disappointing to have my integrity questioned because of a mistake,"

Did it hurt your feelings as much as mine that they questioned his integrity in such an insulting and unpatriotic way? People who would do such a thing are the real terrorists.

Re:We are moving the Roslyn code to GitHub by Joeboy on Sunday January 11, 2015 @05:23AM (#8869603)
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.
Re:We are moving the Roslyn code to GitHub by davidgerard on Sunday January 11, 2015 @05:28AM (#8869610)
It's reasonably easy to pick up your repo and leave.

How easy is it to pick up your bugs and leave?

Re:We are moving the Roslyn code to GitHub by audreyt on Sunday January 11, 2015 @05:56AM (#8869654)
Re:We are moving the Roslyn code to GitHub by sytse on Sunday January 11, 2015 @12:29PM (#8870511)
GitLab B.V. CEO here, on the 22th of this month (January) we'll come out with GitLab 7.7 that includes a GitHub.com importer for both repo's and issues. It will have a simple web interface where you can select the projects to import.
Re:We are moving the Roslyn code to GitHub by spork1 on Sunday January 11, 2015 @05:56AM (#8869656)
Re:We are moving the Roslyn code to GitHub by josteink on Sunday January 11, 2015 @06:31AM (#8869708)
It seems it's pretty easy with Github wikis too:

http://stackoverflow.com/a/22002422

Re:We are moving the Roslyn code to GitHub by pistle on Sunday January 11, 2015 @11:26AM (#8870329)
Private repos cost and there is, and will be, a sufficient demand for such a purpose. Between nuget for package mgmt and github (instead of TFS, etc) you are looking at having important, common pieces available. This makes it extremely comfortable to be in the MS dev camp and still feel that you can interface with others and be sharpening the sword in ways that enable you to build cross platform and potentially jump platforms as necessary.

People have seen experienced .net devs picking up in a wide assortment of communities. Some interpret this as mind flight, or it might just be that the .net ecosystem has made some wise choices that enable devs raised in the ecosystem to not feel their world has silo walls. It's less "no, this" and more "yes, and."

Re:We are moving the Roslyn code to GitHub by josephcooney on Sunday January 11, 2015 @07:34AM (#8869806)
I don't think MS buying github is such a scary thing. There are a few ex-MSFT-ies working at Github (Phil Haack, Paul Betts), and a few other people from the wider MS community there. I guess that is inevitable when Github has 250-ish staff.
Re:We are moving the Roslyn code to GitHub by deanclatworthy on Sunday January 11, 2015 @05:02AM (#8869578)
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.
Re:We are moving the Roslyn code to GitHub by weego on Sunday January 11, 2015 @06:16AM (#8869683)
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.
Re:We are moving the Roslyn code to GitHub by Stratoscope on Sunday January 11, 2015 @06:50AM (#8869739)
> 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 Studio Professional free (as in beer), etc.

Now Oracle, that's a different story. We all still love to hate them!

Re:We are moving the Roslyn code to GitHub by icantthinkofone on Sunday January 11, 2015 @07:03AM (#8869758)
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.
Re:We are moving the Roslyn code to GitHub by aianus on Sunday January 11, 2015 @08:27AM (#8869895)
Apple is more antitrust than Microsoft ever was. Bundling a browser with your OS (while still allowing users to install an alternative) is nothing compared to the restrictions in the iOS app store.
Re:We are moving the Roslyn code to GitHub by xnull2guest on Saturday January 17, 2015 @08:08PM (#8906200)
Right:

- Limiting what compeditor apps are 'up to the standard' for their app store

- Giving their own code and apps special access and APIs that no competitors can have

- Charging competitors for the use of their store

- Ranking of store apps in the favor of Apple code

More importantly the controlling of the ecosystem allows networking effects and developer effects to win Apple money and market share.

Re:We are moving the Roslyn code to GitHub by icantthinkofone on Sunday January 11, 2015 @11:10AM (#8870281)
That's not an "anti-trust" action by itself and bundling the browser was only part of the issue against Microsoft in the US and more of an issue in the EU.
Re:We are moving the Roslyn code to GitHub by cmdkeen on Sunday January 11, 2015 @06:00PM (#8871680)
I grew up hating M$, plus I'm British so we get the whole EU anti-trust thing to boot.

But over the past few years Microsoft has made huge strides, especially the work the two Scotts have put in. Huge amounts of source code open source, their PAAS running all sorts of OSes in VMs, etc.

It isn't the late 90s any more, those that look askance at Microsoft these days seem rather old fashioned given the new shenanigans that are going on.

Re:We are moving the Roslyn code to GitHub by pluma on Sunday January 11, 2015 @09:14AM (#8870010)
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 by lmm on Sunday January 11, 2015 @07:30AM (#8869796)
Remember the dark side of IBM, ten years before Microsoft? And look at how open-source folk treated IBM, even ten years ago. Companies can be rehabilitated.
Re:We are moving the Roslyn code to GitHub by kalleboo on Sunday January 11, 2015 @09:42AM (#8870075)
Also after them buying HockeyApp it wouldn't be the least bit surprising.
Re:We are moving the Roslyn code to GitHub by exadeci on Monday January 12, 2015 @03:18AM (#8872917)
Google is moving code to github too !! :)
Re:We are moving the Roslyn code to GitHub by CmonDev on Sunday January 11, 2015 @05:32AM (#8869617)
That would be great! Next time don't use one provider "cuz' everyone is on GH, dood". Bitbucket is pretty awesome too.