When comparing Haxe vs F#, the Slant community recommends F# for most people. In the question“What are the most enjoyable programming languages for web development? ” F# is ranked 12th while Haxe is ranked 14th. 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 Checks types at compile time
Pro Access native features of target platform
Whenever you need to use target specific code (e.g. there is no Haxe library or extern definitions), you can embed fragments as untyped code in your Haxe code.
Pro Transpiles to Javascript, PHP, Python and many other languages
Pro Dead code elimination
Removes unused types and methods during transpilation.
Pro Checks syntax at compile time
Pro Support multiple different platforms from one source
Pro Easy sharing of code accross multiple target platforms
Pro Provides an exit strategy for Flash developers through OpenFl
OpenFl is a library written in Haxe, that duplicates the Flash API, by providing a parallel implementation.
Haxe's syntax has a lot of similarities with Actionscript 3.
Flash developers can easily migrate their code to Haxe while still using and targeting Flash, in addition to unlocking all the new targets supported by Haxe / OpenFl.
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 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.