Good enough that the gains you get from rewriting your CPU-bound OCaml code in e.g. C++ are usually better than the gains you would get from parallelizing the OCaml.
-
-
Replying to @pcwalton @munificentbob
Yes, but then you would be using C++, and losing out on the benefits of OCaml. Adding multi-core support to OCaml both 1) allows you to gain from multi-core, and 2) allows you to continue using OCaml. Plus, multi-core is tied up with effects, so you gain that benefit too on top
1 reply 0 retweets 0 likes -
your assumption seems to be that there might not be a benefit beyond speed to write in a language
1 reply 0 retweets 0 likes -
Replying to @strega_nil @munificentbob
I’m saying that in practice most people who care enough about speed to go out of their way to parallelize their code for better CPU perf will pick the speed over the language.
1 reply 0 retweets 0 likes -
Replying to @pcwalton @munificentbob
Your logic doesn't make sense. It assumes that parallelism is somehow inherently difficult, *and* that rewriting an OCaml codebase in C++ is somehow feasible.
2 replies 0 retweets 0 likes -
Replying to @strega_nil @munificentbob
Feel free to prove me wrong :) I’m not saying it’s good. I’m just saying what I’ve seen over and over: JavaScript (PJs), Golang, Haskell frameworks, etc.
1 reply 0 retweets 0 likes -
Replying to @pcwalton @munificentbob
C# and Java both support parallelism while being on a level above OCaml
2 replies 0 retweets 0 likes -
The lack of parallelism in OCaml and languages like it is more to do with the age of those languages and the newness of parallelism in mainstream programming.
1 reply 0 retweets 0 likes -
Replying to @strega_nil @munificentbob
Disagree. Parallelism has been around for a long time. The reason is that it’s less effort to just rewrite one’s project in C++ than to parallelize OCaml. So it’s hard to find developers willing to do the work.
1 reply 0 retweets 0 likes -
Replying to @pcwalton @munificentbob
This is only due to design decisions made at the start of OCaml's life, rather than inherent issues with the OCaml model. Rewriting the runtime is a lot harder than you might think!
2 replies 0 retweets 0 likes
I wasn’t saying it’s impossible to parallelize OCaml!
-
-
Replying to @pcwalton @munificentbob
But it is, due to the runtime assuming a single thread.
1 reply 0 retweets 0 likes -
That's the reason it's taken so danged long to get OCaml multicore up and running.
0 replies 0 retweets 0 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.