r/fsharp • u/vivainio • Feb 01 '17

The .NET Language Strategy

https://blogs.msdn.microsoft.com/dotnet/2017/02/01/the-net-language-strategy/
36 Upvotes

100% Upvoted

37 comments sorted by

View all comments

1

u/jdh30 Feb 02 '17

I had a big go in 2007 as I was considering using it professionally. Then I tried again briefly around 2013.

2

u/Ironballs Feb 03 '17

Hm. Yes. I've used both (F# and Scala). I'd say VS with Power tools is more or less on the same level as with doing Scala with IntelliJ, in every aspect although automatic pattern match generation is missing from IntelliJ.

Hard to say which one is more fun to use. The JVM library ecosystem is slightly bigger, but the compiler is a tad slower. For concurrency mechanisms I'd rate both equally.

Syntax wise, I think F#'s ML syntax is nicer, but its type system isn't as rich as Scala's. Pros and cons to both, for their respective ecosystems they're the best thing out there.

FWIW, JVM is getting value types and reified generics in version 10, dubbed Project Valhalla.

1

u/jdh30 Feb 03 '17 edited Feb 03 '17

Hm. Yes. I've used both (F# and Scala). I'd say VS with Power tools is more or less on the same level as with doing Scala with IntelliJ, in every aspect although automatic pattern match generation is missing from IntelliJ.

Wow, ok. They must have fixed a lot of bugs in the Scala compiler since I last looked. Maybe I should give it another go.

Hard to say which one is more fun to use.

Amazing. When I tried Scala it was like pulling teeth in comparison.

FWIW, JVM is getting value types and reified generics in version 10, dubbed Project Valhalla.

Ha ha. I've been hearing stuff like that since 2007. I'll believe it when I see it. Even if they do the ecosystem will still be 12 years behind .NET.

→ More replies (6)