- ambiguous syntax: care to give a few examples?
- inconsistent & incomplete standard library: the library that comes with the compiler is basically the library of the compiler. Opam probably has everything you need.
- shitty REPL. use utop or use emacs. Anyway, I do think people on windows are better of using F#. But that's another discussion.
if a > 0 then
print_endline "a > 0" ;
match a with
| 0 -> print_endline "impossible"
| 2 ->
match b with
| 0 -> print_endline "2, 0"
| _ -> print_endline "2, not 0"
| 3 -> print_endline "3, something"
| _ -> print_endline "something, something"
;
print_endline "done"
You can see the rest of the discussion here: https://news.ycombinator.com/item?id=8497740OPAM saves lives, that's true, but one still wishes there was a nice library of standard data structures; I use Batteries, which inherit the inconsistency of the standard library (for the sake of compatibility), the other real alternative is Core, which is undocumented.
I didn't look at the license very closely, but there are a few forks of the language out there (check out github), which aren't distributed as patches.
To list just the main problems:
- f*-up licence (open-source, but modifications can only be distributed as source-code patches)
- non-concurrent runtime (because the original developers don't care about it)
- ambiguous syntax which masks bugs
- inconsistent and incomplete standard library (there are replacements, but they too suck)
- shitty REPL (at least on Windows)
Well, that's about it. It's really fast, safe, expressive, as functional as it gets ([EDIT] also: compiled). Definitely one of the better-designed languages, and a great starting point for many other languages (F#, Swift, Rust).
Lately, there has been a lot interesting development that eased development in OCaml (basic overloading, this IDE), and more seems to be coming (concurrent GC/runtime).