Live data from Hacker News

Microsoft Launches Its .NET Distribution for Linux and Mac

techcrunch.com

101–110 of 249 posts

Re: Microsoft Launches Its .NET Distribution for Linux and Mac

#101

I'm curious, is there enough released yet to build server-side web apps? Would there be an apache mod, or some other web server? Or is there something more akin to a node app? I really enjoy C#, but everything that I did was either a Windows-only desktop app or a web app served through IIS. Thanks for any insight.

Yes, you can do this now.

https://github.com/aspnet/Home/tree/dev/samples/latest/Hello...

Follow instructions here: https://github.com/aspnet/home

This can also be done with mono, fastcgi, and nginx.

http://www.mono-project.com/docs/web/fastcgi/nginx/

Re: Microsoft Launches Its .NET Distribution for Linux and Mac

#103

I'm curious, is there enough released yet to build server-side web apps? Would there be an apache mod, or some other web server? Or is there something more akin to a node app? I really enjoy C#, but everything that I did was either a Windows-only desktop app or a web app served through IIS. Thanks for any insight.

ASP.net web apps have been possible on Linux without IS for many years.

Re: Microsoft Launches Its .NET Distribution for Linux and Mac

#104
post #84

They mercifully waited until Java caught up a bit with version 8. Seriously, they could have fair chance, C# was so much better, but today it's still quite better but java is proven and has more libs.

Java, with Oracle at the wheel, is not going anywhere. They've added closures in 8, big deal. C# is centuries ahead of Java 8, and with even more to come faster. And I'm saying that as an old Java dev (for 8 years up until 2008 or so) who have only dabbled in C#.

Ehhh, When Sun was at the helm Java was stuck in quicksand even worse than today. Its only a few years ago.

Re: Microsoft Launches Its .NET Distribution for Linux and Mac

#105
post #75

Earlier quoted context omitted.

Think of it as like the Java runtime environment, but not terrible. You have two main pieces: the Common Language Runtime, which is the virtual machine (like the JVM) that executes the code. Then you have the library it comes with, which is fairly large compared to most languages. edit: Added more context

One of the interesting things I'm waiting to see is if .NET gets good enough to become the "main" platform for compile to VM languages like Clojure. It can already compile to .NET, but it's significantly less used than the JVM version, despite .NET generally being easier to target.

People have been using the CLR like that for many languages for many years. Maybe you didn't hear about it because it was a Windows thing.

.NET was good enough when it came out many years ago. It was just a closed one platform thing.

Re: Microsoft Launches Its .NET Distribution for Linux and Mac

#107

Earlier quoted context omitted.

So, why would a Mac user develop in it, instead of in a Windows (virtual) machine? How would .NET compare to Apple's native environment? I guess the whole point is to write cross-platform code, but is the .NET environment that much better than Swift/Xcode? I mean, Java never really caught on with the Mac user base.

> I guess the whole point is to write cross-platform code, but is the .NET environment that much better than Swift/Xcode? You said it all. The whole point is cross platform development. People use Swift to develop apps for Apple products. Before Dot.net was made open source, people only used it to develop for Microsoft platforms. The fact Dot.net is now crossplatform makes it possible for GNU/Linux and Mac users to c…

So when will Swift be made open-source?

I am not going to make the same mistake twice and be tied down to a language (Objective-C) and private APIs (Cocoa, iOS, etc) which are useless outside of Apple's ivory tower.

I had always thought of C# and Mono as a potential cross-platform solution, but now that .NET is open-source and Microsoft are pushing it hard, even on Linux, it has become a viable one.

I suspect I am not the only Mac->iOS developer who is thinking along these lines.

Re: Microsoft Launches Its .NET Distribution for Linux and Mac

#108
post #31

This is interesting but is there any commitment to support it long term? I remember when Silverlight was supposed to be the savior that brought .NET to Mac and Linux, but that didn't last more than 5 years. Would be nice for MS to say they guarantee support for 10, 15, etc. years.

This is the thing with Microsoft is this is never in doubt. It is Google who ends of life's things and stops support. Microsoft still has supports things in Windows 8.1 that were BUGS in MS-DOS in order to allow programs from that era to run.

Microsoft will support .NetCore for at least 20 years. Without doubt.

Re: Microsoft Launches Its .NET Distribution for Linux and Mac

#109
post #28

F# is a real breath of fresh air in comparison to something like Scala. It's direct ML heritage really shows, also just diving in with an IDE (like Xamarin, or I suppose Visual Studio) is super easy. I see it as the future of pop-functional programming. For example look at the way it handles type inference w/ JSON parsing. Compare that to what you have to do to parse JSON in Scala. It's subtle, but a major usability…

Did you just invent a term? "Pop-Functional"... I like it!

Re: Microsoft Launches Its .NET Distribution for Linux and Mac

#110

Earlier quoted context omitted.

It is like the Java runtime, but started afresh with all of Java's learned lessons taken into account (although Java with 7 and 8 in particular is catching up). Up until now however it has only ran on Windows which was its biggest "downside" Vs. Java which runs on many platforms.

> started afresh with all of Java's learned lessons taken into account I don't think that's really historically accurate. Java and C# were pretty similar back in 2002. The .NET team was more willing to add complexity and occasionally make breaking changes, like generics in CLR 2.0.

That's not historically accurate either. The .Net team was more willing to break things because in 2002 they had their 1.0 release. By then Java had already lived through 6 years of very aggressive presence in the marketplace, with lots of legacy code already in the wild. The only legacy MS had to worry about was COM, which had its own compatibility wrappers that were not fundamentally intrinsic to the CLR.

So .Net had the advantage of coming years after Java had shown what it could be done (or not, see browser applets) from a technological and commercial point of view, AND quite a few years of development without worrying about backward compatibility.

I'm not saying Sun developers were not slow (they were), but they clearly had a much more "entrenched" position, with all that it entails.

Post reply on HN