3 ms·
I'd suggest try both. The Elixir web world gets a lot more love than the F# one. F# always touts the advantage of living in the .NET world, but it means most
by keithnz 8y ago
I'd suggest try both.
The Elixir web world gets a lot more love than the F# one. F# always touts the advantage of living in the .NET world, but it means most things are built with C# in mind, not F#. There are F# frameworks, and they are nice, but the community is quite small. But the advantage is the .NET world has a vast amount of libraries for doing most things.
OTP and Elixir is a better story than F# equivalents. There are no lightweight isolated processes in .NET
Elixir also has macros ( a very sharp double edged sword ) which can make frameworks nice to use.
F# is stronger typing which is nice and often has the trait if it compiles, it works. Though the normal downsides of dynamic typing in Elixir are not so bad.
But the best thing is to try both and make up your own mind
- rienbdj 8y agoF# async and mailbox provide a decent actor model. Writing an F# wrapper on c# libraries is usually very easy. You can also call c# code directly and it doesn’t look too bad. Computation expressions can fulfil the needs of macros in many cases in a controlled way.