61–70 of 459 posts
Everyone on Roslyn is really excited about this and we hope that it serves as a signal that big things are happening in .NET to make the entire platform more open and agile! P.S. We're the Visual Basic compiler too :)
Everyone on Roslyn is really excited about this and we hope that it serves as a signal that big things are happening in .NET to make the entire platform more open and agile! P.S. We're the Visual Basic compiler too :)
So does that mean one can reasonably expect to use official F# implementation(compiler, vm, libraries) in Linux within the coming months/years?
Lots of people use it
Earlier quoted context omitted.
It's a compiler. It takes input and produces output. There shouldn't be much in there that has any platform dependency.
For any compiler, platform-dependence of the compiler itself is strictly tied to platform-dependence of outputs. Edit: I confused roslyn with the recently announced AOT compiler.
Wow these contributions are a huge deal for Mono. I've spent the last few months making sure C# code works well in Mono and there are a lot of things that are missing or buggy. WebClient for example on Mono is missing DNS refresh timeout which means your app will never update a dns cache entry. If the ip of a server changes, you're pretty much screwed in Mono.
This doesn't solve your issue with WebClient. This is only a compiler and not runtime.
No more ".Net magic" now that the curtain's dropped. I think this will help .Net devs make smarter decisions about their code now that they can see what's happening in the background.
They also announced as part of this that they are putting a large swatch of their .NET Source code under Apache 2 and accepting pull requests. Folks, this is a very big deal for Microsoft. Who would have imagined this 10 years ago? Here is an image that shows what they are putting into the community https://pbs.twimg.com/media/BkT9oBcCQAAHIAV.jpg:large
... as awesome as this is, I'm gonna be That Guy: No WPF?
Earlier quoted context omitted.
Quite a lot of people actually. These moves have been on the cards for years. Just waiting now for the next big move in the coming months of when they acquire Xamarin.
I was hoping there would be an announcement at Build that they had acquired Xamarin, but that didn't happen. All that was mentioned was that they were a partner that they were working with. Still a possibility in the future though. The open sourcing of Roslyn can only mean good things for Xamarin.
Wow these contributions are a huge deal for Mono. I've spent the last few months making sure C# code works well in Mono and there are a lot of things that are missing or buggy. WebClient for example on Mono is missing DNS refresh timeout which means your app will never update a dns cache entry. If the ip of a server changes, you're pretty much screwed in Mono.
This doesn't solve your issue with WebClient. This is only a compiler and not runtime.
No more ".Net magic" now that the curtain's dropped. I think this will help .Net devs make smarter decisions about their code now that they can see what's happening in the background.
I'm not sure whether there ever was a time when .NET devs had to seriously consider "what was happening in the background". .NET Framework documentation has always been pretty good. Not too many dark corners there.