Live data from Hacker News

Microsoft takes .NET open source and cross-platform

news.microsoft.com

101–110 of 937 posts

Re: Microsoft takes .NET open source and cross-platform

#101

It will be interesting to see how this will work in practice. C# will port over just fine. But the .Net libraries? System.Windows has little to nothing in it, and right now using things like System.IO.* on Linux and Mac is just asking for trouble. What are they going to do, hack in System.IO.* Linux support after the fact? Or just add Linux.IO.* which is even more of a hack. In either case you're going to get very me…

Microsoft's focus on this release is the server.

Mono plans on contributing to the effort our cross platform changes to Mono, to make .NET work great on Unix.

Details here: http://tirania.org/blog/archive/2014/Nov-12.html

Re: Microsoft takes .NET open source and cross-platform

#104

According to Scott Hanselman they are also open sourcing their new RyuJIT and even the GC. Incredible! http://www.hanselman.com/blog/AnnouncingNET2015NETasOpenSour... or http://webcache.googleusercontent.com/search?q=cache:http://...

Apparently the .NET runtime and Mono will merge:

https://twitter.com/shanselman/status/532558786486370304

Re: Microsoft takes .NET open source and cross-platform

#105

It will be interesting to see how this will work in practice. C# will port over just fine. But the .Net libraries? System.Windows has little to nothing in it, and right now using things like System.IO.* on Linux and Mac is just asking for trouble. What are they going to do, hack in System.IO.* Linux support after the fact? Or just add Linux.IO.* which is even more of a hack. In either case you're going to get very me…

I don't think they are open sourcing the client libraries like WPF and Win Forms. Like you are alluding to, what good would it do if they did since it is 99% Windows only functions in there.

They are open-sourcing the server side code. I think this means your ASP.Net apps can run on Windows, Linux, Mac OSX all from the same open source code base. No worry about Mono incompatibilities and bugs.

Re: Microsoft takes .NET open source and cross-platform

#106

What happens to Xamarin business model now?

It improves it.

We now get all these bug fixes for all of our products across Android, Mac, iOS, PlayStation, Xbox and every other embedded system we support.

Some details:

http://tirania.org/blog/archive/2014/Nov-12.html

Re: Microsoft takes .NET open source and cross-platform

#107

What happens to Xamarin business model now?

It improves it.

We now get all these bug fixes for all of our products across Android, Mac, iOS, PlayStation, Xbox and every other embedded system we support.

Some details:

http://tirania.org/blog/archive/2014/Nov-12.html

Re: Microsoft takes .NET open source and cross-platform

#108

Too little, too late. At the end of the day, you're still being forced to pay a company to use their shitty software. Once you lose developers, you lose the race.

The thing is, it's anything but shitty.

C# is one of the best languages out there for generic enterprise work and app development, and there's a magnigicent next gen language in F# thrown in, and a great web framework.

Re: Microsoft takes .NET open source and cross-platform

#110

It will be interesting to see how this will work in practice. C# will port over just fine. But the .Net libraries? System.Windows has little to nothing in it, and right now using things like System.IO.* on Linux and Mac is just asking for trouble. What are they going to do, hack in System.IO.* Linux support after the fact? Or just add Linux.IO.* which is even more of a hack. In either case you're going to get very me…

Mono has been doing just fine. Yes, you can't rely on WinForms, even though a port exists. You can't do COM, that's for sure. But that doesn't mean that Mono is not valuable for what it is right now.

Microsoft doesn't need to provide compatibility for the Windows specific bits, as those bits are not part of the Core. And a platform like .NET has enough value in open-sourcing just the Core (i.e. whatever goes in the ECMA standard). For example it's a perfectly acceptable strategy to use GTK# on Linux, WinForms on Windows, MonoMac on OS X and Xamarin.Whatever on iOS / Android.

On System.IO, indeed there are differences between Winsock and Linux's epoll or BSD's kqueue (i.e. notify on completion versus notify on ready). There are differences between the 2 models, but I don't see that as a problem for System.IO and if you think it is a problem I'd like to read an explanation as to why.

Personally I'm very excited about this announcement. I avoided .NET for years and preferred to settle for the JVM because I do not like building on top of proprietary things. If they are really open-sourcing the .NET runtime, whilst uniting their efforts with Xamarin, that's really good news. Now hopefully the ecosystem around .NET will follow, as .NET needs an open-source oriented ecosystem and needs one badly.

Post reply on HN