3 ms·
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 [
by xvilka 8y ago
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 https://github.com/ocamllabs/ocaml-multicore
[2] https://github.com/garrigue/lablgtk https://github.com/garrigue/lablgtk
[3] https://github.com/garrigue/lablgtk/issues/2 https://github.com/garrigue/lablgtk/issues/2
[4] https://caml.inria.fr/mantis/roadmap_page.php https://caml.inria.fr/mantis/roadmap_page.php
[5] https://github.com/ocaml/opam/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+Windows 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/ http://opam.ocaml.org/blog/opam-2-0-0-repo-upgrade-roadmap/
- shikoba 8y agoWe use OCaml on windows everyday and have no problems with it. Since the support of foreign encoding (recent) there is no major issues with OCaml. The support is not perfect, but you can't say that it's bad.