News for hackers. Stuff that matters.
Re:The .NET Language Strategy by xenadu02 on Wednesday February 01, 2017 @06:38PM (#13546570)
Microsoft took the hit and revamped the runtime when generics landed. I'm sure they would take another hit if such a critical feature presented itself and there wasn't a good way to retrofit it.

The only two warts that strike me off-hand are covariant arrays and System.Nullable being value-type only.

Overall Microsoft has done a great job of building on earlier decisions. Including functions as first-class types (System.Delegate) in V1 is probably the biggest and was a deliberate break with Java's approach. It has enabled a ton of features: lambdas, LINQ, Expression, etc. The fact that LINQ can be turned into an AST with Expression<T> means you can also construct code dynamically at a much higher level than IL.Emit() while delegates mean you can get the JIT to provide the equivalent of a function pointer to the native code.

Re:The .NET Language Strategy by pjmlp on Thursday February 02, 2017 @03:06PM (#13554090)
Actually they had it "almost" done before 1.0, but they didn't want to delay the release any longer.

https://blogs.msdn.microsoft.com/dsyme/2011/03/15/netc-gener...