Announcing .NET Core 2.0

Re:Announcing .NET Core 2.0 by jackfoxy on Monday August 14, 2017 @01:53PM (#15010777)

The problem is F# does not use the Roslyn compiler (but does use other components of the Roslyn tool stack in Visual Studio) and it uses things in the IL (primarily tail calls) the other .NET languages do not -- and the rest of the Microsoft teams understandably want to move fast on all the initiatives surrounding .NET Core.

This results in the Microsoft F# team and the F# community contributors playing catch-up. Eventually F# will catch-up, but it is going to take time.

[ Parent | on HN ]

Re:Announcing .NET Core 2.0 by TensorMetric on Monday August 14, 2017 @04:16PM (#15012431)

Microsoft's own .NET Native runtime is simply not .NET compliant https://news.ycombinator.com/item?id=15007166

This is unacceptable and should be fixed ASAP. F# is a mature language existing for more than a decade, there is simply no excuse to let this slide.

[ Parent | on HN ]

Re:Announcing .NET Core 2.0 by jackfoxy on Monday August 14, 2017 @05:05PM (#15012890)

Microsoft had to fix the C# compiler. The result was Roslyn. It's actually amazing that Roslyn was a successful project. Probably most software projects that ambitious fail. The project would have failed if they tried to make it F# compliant at the same time.

Speaking as someone who makes his living writing F# code, I'm as frustrated as anyone about this, but there will be a successful resolution. I just don't know how soon. Before today's announcements my personal thinking was that it would be this autumn. That's still possible. In the meantime I can still function in the F# world, as before. It just remains frustrating to branch out into some of the areas I would like to.

[ Parent | on HN ]

Re:Announcing .NET Core 2.0 by TensorMetric on Monday August 14, 2017 @06:28PM (#15013605)

If it's going to be fixed this year, then why isn't it even on the official road map? https://github.com/Microsoft/visualfsharp/issues/2400

[ Parent | on HN ]

Re:Announcing .NET Core 2.0 by jackfoxy on Monday August 14, 2017 @07:59PM (#15014162)

You're absolutely correct about .NET native not being .NET compliant...sigh...there are just higher priorities for such a big company. As quoted in the comments " [F# native support] depends on the Core CLR team improving support for a couple of big items. dotnet native is and AOT compilation are absolutely a goal for us ... they just are longer term than this roadmap anticipates."

It's actually eye-opening how few the number of people at MS who actually write code is. I suppose if there were more coders they would be stepping all over each other and never get anything done.

[ Parent | on HN ]

Re:Announcing .NET Core 2.0 by pjmlp on Tuesday August 15, 2017 @01:52AM (#15015847)

Politics more likely.

[ Parent | on HN ]

Re:Announcing .NET Core 2.0 by jackfoxy on Monday August 14, 2017 @08:09PM (#15014226)

You might want to take a look at this announcement RE: F# https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net... (does not mention native, but does address other deficiencies)

[ Parent | on HN ]

Re:Announcing .NET Core 2.0 by pjmlp on Monday August 14, 2017 @03:39PM (#15012047)

F# was supported on the MDIL compiler for Windows 8.x, then Microsoft did not consider the language relevant enough to support on the new .NET Native compiler when Windows 10 came out, almost two years ago.

How much time do they need to catch up?

[ Parent | on HN ]