corefx

Funny you should ask..I started this journey right here on HN. Still yet again haven't had time to get back into it but I will take your comment as a suggestion to try harder to find time for this. There is more information about this here (if you are interested in the answer to "why" it hasn't made it yet): https://github.com/dotnet/corefx/issues/10610

Most of the big MIT licensed Microsoft projects I know (.Net Core VM and libraries) are licensed under MIT with a separate, explicit patent grant. For example look at the PATENTS.TXT file in this repo: https://github.com/dotnet/corefx

The problem of these licenses is that they don't come with patents grants. Which given that this is Microsoft we are talking about, it's a big deal. Of course, their projects does come with a patents license, in addition to the copyright license, but it's unclear to me whether this license applies to derivative works for example. I'm not a lawyer of course and I have a very limited understanding, but interpreting their license as an English text, I really don't think it applies to derivate works. Would like an analysis of somebody knowledgeable, because a project that can't be safely forked isn't open source. Here's their license: https://github.com/dotnet/corefx/blob/master/PATENTS.TXT Anyway, my point is that I would have preferred something like the Apache License, which is still permissive, but was written by lawyers that know what th

Compiler and compilation-related bugs are quite interesting to come across, since they can produce truly mind-boggling behavior. A while back we ran into this one in the .NET jitter while working on ASP.NET Core: https://github.com/dotnet/corefx/issues/8825

There are new platform targets that cover the common functionality. Support in NuGet is a bit nascent though. https://github.com/dotnet/corefx/blob/master/Documentation/a...

Any ideas how to do GUI development with .NET Core? Is there a version of Xamarin? Are there plans to port Windows.Forms, WPF? There is this massive thread about it http://forums.dotnetfoundation.org/t/cross-platform-wpf/421/... and an issue here https://github.com/dotnet/corefx/issues/5766

I was expecting they would fix the Uri class on Unix (https://github.com/dotnet/corefx/issues/1745) before releasing 1.0 :( Now I fear their backwards compatibility policies will prevent to fix it later. So much for crossplatformness...

Datatables are not gonna make 1.0, and I think it is underestimated how much they are still in use: Longread which gives I nice overview: https://github.com/dotnet/corefx/issues/1039 DbProviderFactory: https://github.com/dotnet/corefx/issues/4571 Schema stuff: https://github.com/dotnet/corefx/issues/3423 https://github.com/dotnet/corefx/issues/5024 I don't care that much for schema as I'm not an ORM writer, but I do have used Datables a lot as a convenient data-mangler type for importing legacy data, converting data etc. They may be "dirty", obsolete or whatever but they get the job done.

Depends on how you learn. Some learn by being around others, social interaction, asking questions and absorbing knowledge. It's clear you fall into the latter category which likes to learn by diving right into the code, so here it is: .NET CLR Managed Runtime - https://github.com/dotnet/coreclr .NET Framework - https://github.com/dotnet/corefx .NET Compiler as a Service ("Roslyn") - https://github.com/dotnet/roslyn .NET Orleans Actor Framework - https://github.com/dotnet/orleans Mono Framework - https://github.com/mono/mono Xamarin iOS, Watch, Mac Bindings and Framework - https://github.com/xamarin/xamarin-macios Xamarin Android Bindings and Framework - https://github.com/xamarin/xamarin-android

Arbitrary requirements much. By your own logic if Linux were a Microsoft product that wouldn't be good enough because it is only GPLv2. A lot chunk of the .Net framework are under MIT license and include this: https://github.com/dotnet/corefx/blob/master/PATENTS.TXT Seems pretty comprehensive to me.