News for hackers. Stuff that matters.
Re:The Early History of F# [pdf] by lmm on Friday January 11, 2019 @11:41AM (#18884689)
Why not Scala? That's a very similar language to F#, and JVM interop would let you do a gradual migration.
Re:The Early History of F# [pdf] by saberience on Friday January 11, 2019 @11:49AM (#18884757)
The scala toolset is incredibly crap though. Ask the engineers on my team about the huge pains of transitioning to using IntelliJ from Visual Studio, or the joy of trying to make SBT do what we want it to do, then trying to use Maven instead.

Any new engineer we get started with Scala has to spend about a week making their local setup work. It's a total pain in the arse.

Re:The Early History of F# [pdf] by lmm on Monday January 14, 2019 @09:29AM (#18903153)
SBT is awful (so ignore it); Maven is wonderful. Visual Studio is very good, but grandparent said their code was previously in Java, in which case their team will already be used to IntelliJ or Eclipse, and it's F# that would involve making a transition.
Re:The Early History of F# [pdf] by adgasf on Friday January 11, 2019 @11:43AM (#18884702)
We wanted to make significant changes, so a gradual migration would not have been possible regardless of language. Regarding Scala vs F#, I do not know enough Scala to comment. Perhaps someone else can weigh in?
Re:The Early History of F# [pdf] by bunderbunder on Friday January 11, 2019 @01:31PM (#18885638)
I've spent a fair bit of time with both. Personally, I don't find the two to be all that comparable -- they're fairly distant cousins.

F# tends to stick much more closely to its ML roots, and fairly scrupulously retains a more ML flavor except when necessary to achieve good interop with the .NET ecosystem.

Scala, on the other hand feels less to me like a dialect of ML and more like an ML-flavored object-oriented language, because it mixes in OOP-style features much more freely. Its algebraic data types, for example, are explicitly implemented as class clusters. A lot of people like this, others see it as an anti-feature. Where you fall probably depends on how you feel about the relative merits of OOP and FP.

It's also, for better or worse, less concerned with maintaining good interop with the rest of the ecosystem. Consuming F# modules from C# isn't always pretty, but it's always possible. There will be C#-friendly wrappers, but creating them is a matter of aesthetics rather than necessity. Consuming Scala modules from Java, though, frequently requires creating wrapper libraries. On the upside, this does mean that Scala gets to have things like typeclasses, which the F# team has kept out of the language due to concern about how they would impact interoperability with the rest of .NET.

Last but not least: F# has type providers. Scala has implicits. F# has quotations. Scala has more stuff that's also called implicits.