News for hackers. Stuff that matters.
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?