Standard ML vs F#
When comparing Standard ML vs F#, the Slant community recommends F# for most people. In the question“What are the best languages for learning functional programming?” F# is ranked 3rd while Standard ML is ranked 15th. The most important reason people chose F# is:
F#'s syntax tends to be terse while remaining very readable and easy to understand without being a chore to write.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Powerful module system
The module system that Standard ML uses gives the programmer the power to define custom data types whose internal implementation is invisible to other programmers using the module.
Pro Implementing laziness is trivial
Since mutability is only confined to a special type of reference cells, implementing laziness in SML can be done in only 20 lines of code.
Pro Enforces distinction between data and computations
Since it uses strict evaluation, it enforces distinction between data and computations which in turn enables you to use induction on algebraic data types as a reasoning principle.
Pro Great exception system
Secret messages can be sent across distant parts of a program without possibility of being intercepted by unintended recipients in the middle.
Pro Concise syntax
F#'s syntax tends to be terse while remaining very readable and easy to understand without being a chore to write.
Pro Easier transition from other paradigms
Since F# is not a purely functional language, it lends itself to being more easily picked up by programmers that have experience with other paradigms.
Pro .NET Interoperability
Since F# runs on the Common Language Runtime or CLR, it has access to the entire .NET Framework, as well as libraries written in other .NET languages such as C#, VB.NET, and C++/CLI.
Pro Multiplatform, it runs on .Net Core
Forget Xamarin and Mono. F# now runs on the multiplatform .Net Core!
Pro You can run F# in the browser
Thanks to a project like Fable, you can write and run your client app in F# and run it over JavaScript. It allows you to share code between your server and client.
Pro Natively supported by Visual Studio
This is a .Net language natively supported by Visual Studio. Though it is not as tooled up as C# the support is still substantial. In particular, C# deployment scenarios can be enabled for it with small C# wrapper projects. Integration with Visual Studio provides: IntelliSense, debugging, projects an other features.
Pro Fall into the pit of success
F# directs you into a workflow where the right way is the path of least resistance.
Coming from a C# background, its restrictions might feel arbitrary at first (e.g., what do you mean my code has to be in dependency order!? Arbitrary alphabetical or bust!), but you'll soon realize that your code is cohesive, concise and consistent in a way that it never was before - and you can compile and run with confidence!
Pro F# is supported by Xamarin
Thanks to Xamarin, F# is a functional language that you can use to build for iOS, Android and Windows.
Cons
Con Not very popular outside academia
SML is mostly used in academia and doesn't have many uses in industry. While it's a good language for learning functional programming concepts, the language itself won't be very useful.
Con Has no ad-hoc polymorphism (á la Type Classes)
You have generics, you have interfaces, you have inheritance, you have a lot of things at your disposal but you don't have Type Clases. They can be emulated using some clever constructs but there's nothing like having the real thing.
Con Infested with OOP
Still relying on .NET OOP libraries.