3 ms·
The complaints I remember about ocaml the last time I checked it out were related to multithreading. No idea if that's changed. But I do see ocaml very often in
by sfRattan 6y ago
The complaints I remember about ocaml the last time I checked it out were related to multithreading. No idea if that's changed. But I do see ocaml very often in use to write a compiler, especially for languages that aren't yet self-compiling, most recently when looking into Haxe.
- cptwunderlich 6y agoNot yet, but it's a work in progress: https://discuss.ocaml.org/t/multicore-ocaml-february-2021/7449/3 https://discuss.ocaml.org/t/multicore-ocaml-february-2021/74...
- yawaramin 6y agoNode.js, Python, and Ruby are single-threaded. They all have ways to achieve concurrency and multi-process usage right now, and so does OCaml. I get it, people really want OCaml multicore–and it's coming–but that by itself is not stopping OCaml from being an industrial-strength, production-ready language right now.
- pjmlp 6y agoFor generations, the only way to use multiple CPUs was multiple process and asynchronous syscalls. So for C it was ok, but for OCaml a reason not to use the language.