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