News for hackers. Stuff that matters.
Re:.NET Framework – What's New in C# 7.0 by int_19h on Thursday November 17, 2016 @04:25AM (#12975833)
A big problem wrt speed of evolution of NET historically has been the legacy design of the BCL, and the fact that it's updated as one monolithic thing when a new .NET version is released.

The new model used by .NET Core is to make everything a NuGet package; and not a single big one, but small packages comprising one particular bit of functionality, each of which can then be versioned separately. For example, collections are a NuGet package:

https://www.nuget.org/packages/System.Collections/

With this model, it's possible to iterate on the API much faster, so my expectation would be to see functional APIs in the standard library spread much faster from now on.

Re:.NET Framework – What's New in C# 7.0 by ygra on Thursday November 17, 2016 @04:37AM (#12975903)
Interestingly they thus have effectively an equivalent of Java's long-awaited and long-postponed Project Jigsaw. It seems to not have been such a roadblock for MS, maybe also because of a somewhat shorter history of the platform (no idea how comparable the code inside is regarding spaghetti-ness and interdependencies).
Re:.NET Framework – What's New in C# 7.0 by oblio on Thursday November 17, 2016 @05:06AM (#12976068)
I think it's more due to Sun dropping the ball and Oracle not putting the same amount of resources behind Java as Microsoft puts behind .NET.
Re:.NET Framework – What's New in C# 7.0 by louthy on Thursday November 17, 2016 @01:49PM (#12980198)
I agree that the BCL is better off as separate packages (even if it's caused many headaches getting my NETCore build right); but my main point was that the BCL is pretty much 100% stuck in OO-land. Aside from a few types and interfaces (DateTime, string, IEnumerable, IObservable, ...), there's no coherent functional base for C#: no Option type, by default the collections are all mutable (the immutable versions have terribly awkward names like ImmutableDictionary, etc.), lots of void returning methods, etc.

I could go on, but there's not a huge point to moaning about it, which is why I decided to do something about it. I'm not sure if it's even possible for there to be an official functional BCL without it being a totally new set of packages. It's something that F# would benefit from too.