News for hackers. Stuff that matters.
Re:Announcing .NET Core 2.0 by banashark on Monday August 14, 2017 @01:24PM (#15010489)
I'm enjoying reaping the rewards of all the dotnet core work in my F# projects.

One critique:

Why break semver?

https://github.com/dotnet/standard/blob/master/docs/faq.md#w...

Like I get that it feels like a big change (and it is), but you've gone and confused a huge population of library writers and users with the major version bump.

https://github.com/search?q=netstandard2.0&type=Issues&utf8=...

How many of those are irrelevant or invalid? That's just github. I already see the noise being created in slack and gitter channels as well.

Other than that I think dotnet core is an amazing engineering effort and I've been happy using F# on OSX with it.

Re:Announcing .NET Core 2.0 by terrajobst on Monday August 14, 2017 @02:42PM (#15011305)
It doesn't break sem ver. Sem ver doesn't disallow revving the major number without making a breaking change. It only says if you do a breaking change, you need to rev the major number.
Re:Announcing .NET Core 2.0 by sridca on Monday August 14, 2017 @02:59PM (#15011522)
Is there a good open source F# project running on .NET core? Just to see what it looks like.
Re:Announcing .NET Core 2.0 by bsaul on Monday August 14, 2017 @01:28PM (#15010537)
do you still need to install mono in addition to core to get autocomplete on vscode ?
Re:Announcing .NET Core 2.0 by banashark on Monday August 14, 2017 @01:35PM (#15010602)
Re:Announcing .NET Core 2.0 by yawn on Monday August 14, 2017 @01:55PM (#15010804)
Also for fsharp interactive support Also for type providers support

Things are very hit or miss in F#-land with .NET Core.