4 ms·
Not the grandparent, but... OCaml: multicore, standard library situation (which one?) is a mess, adoption. F#: Have to deal with null and lack of ADTs when you
by yawn 7y ago
Not the grandparent, but...
OCaml: multicore, standard library situation (which one?) is a mess, adoption.
F#: Have to deal with null and lack of ADTs when you interact with .NET (or JS for Fable) standard lib. The tooling situation in F# has been a mess since .NET Core, especially in Linux. Treated as a 2nd class citizen by MS.
- msvan 7y agoMulticore OCaml is actually making promising progress, but I agree that the standard library situation is a little bit unfortunate.
- ynnn 7y agoSadly, that's what I've been hearing for at least 5 years.
- akra 7y agoI'm using F# tooling in Linux and both VS Code and Jetbrains Rider's IDE's outclass most functional language IDE's at present IMO. It's greatly improved within the last year or so. If you use code most of your app in F# the null factor doesn't really bite you all too often and its not too hard to handle when it does.