opam

Speaking of problems, in my opinions the three biggest are: - Lack of automatic multicore scheduling, this is going to be solved with OCaml multicore project [1] - Lack of updated GUI libraries. There is LablGTK [2], but it stuck to GTK+ 2 version. The main developer started [3] to work on GTK+ 3 version support, but it is still at the very beginning. - Bad Windows platform support [4] (grep for "Windows" word at this page) and [5]. With upcoming opam-2.0 [6] release the support will be slightly better though. [1] https://github.com/ocamllabs/ocaml-multicore [2] https://github.com/garrigue/lablgtk [3] https://github.com/garrigue/lablgtk/issues/2 [4] https://caml.inria.fr/mantis/roadmap_page.php [5] https://github.com/ocaml/opam/issues?utf8=%E2%9C%93&q=is%3Ai... [6] http://opam.ocaml.org/blog/opam-2-0-0-repo-upgrade-roadmap/

I'd say if you ever get the time again, give OCaml another look. The toolchain experience has been improving at a rapid pace! I started to explore OCaml again earlier this year and the day to day tooling around it has felt at par or better than my experience with other languages. Between Opam [1], Dune[2] and utop[3] the "new comer experience" has been really good so far. The editor integration with vim/emacs has been top notch, and visual studio code has turned into a really nice option as well for people who don't like vim/emacs. I'm sure there is still room for improvement, but i'd say its atleast heading in the right direction! [1] https://github.com/ocaml/opam [2] https://github.com/ocaml/dune [3] https://github.com/diml/utop [4] https://github.com/ocaml-ppx/ocamlformat