28 ms·
I've tried OCaml a few times over the years, and I think its biggest problems are chicken/egg problems. It's impractical for "real world" use because not many
by jlarocco 15y ago
I've tried OCaml a few times over the years, and I think its biggest problems are chicken/egg problems. It's impractical for "real world" use because not many people are using it in the real world.
My biggest complaints:
* Poor libraries - This is getting better, but it used to be a real pain to do stuff like make an HTTP request, parse JSON or XML, or connect to a database. They definitely weren't in the stdlib, and it was even pretty hard to find good third party libraries for it.
* Awkward library interfaces - Even the libraries that are included are awkward to use, like the Set and Map.
* Poor documentation - There's nothing (or was nothing) like http://perldoc.perl.org/ http://perldoc.perl.org/ or http://docs.python.org/ http://docs.python.org/
And, off-hand, one language nitpick:
* Poorly handled strong typing - For example '+' is used to add integers while '+.' is used to add floats. The underlying reason makes sense, but there's awkward stuff like that all over. Haskell handles it better, IMO.
- avsm2 15y agoThe first three are indeed a big irritation, and a big motivation during writing this book. There is a lot of work going on to improve all of these at the moment, notably through Core from Jane Street providing a well-maintained accessible standard library, and a convergence of packaging systems. The good folks at OCamlPro are also working hard to better editor and documentation support, so I except there will exist a documentation/package repository before this book is released.
- gaius 15y agoconnect to a database This is something I have been working on http://gaiustech.github.com/ociml/ http://gaiustech.github.com/ociml/