Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It supports parallelism the same way UNIX clones did for their first two decades, which is quite good for plenty of workloads, and then there is Lwt for concurrency.

And it is safer. :)

In any, case multicore runtime is getting closer, https://discuss.ocaml.org/t/multicore-ocaml-january-2020-upd...



If we have to mention inter-process communication where every process is single-threaded then IMO the battle has been lost.

Best IPC is no IPC, wouldn't you agree? In-process function calls can't be beaten.

Give me a mix of OCaml and Rust with the runtime of Erlang/Elixir and I ain't learning another programming language until the day I die!

Thank you for the link, I found it really interesting.


In the times of Spectre, Meltdown and in-process exploits due to threading issues, everyone doing microservices, I don't see the inter-process communication route as that bad.


Sure, pretty good point actually.

I'm just saying that in these same times many problems fall into the category of embarrassingly parallel and there's no reason to wait 4s for a result that can easily take 0.5s.

But you're also correct.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: