what's the state of this nowadays?
> better Windows support
couldn't agree more - they can learn on Go's lessons (the language didn't get much traction until they added Windows support).
what's the state of this nowadays?
> better Windows support
couldn't agree more - they can learn on Go's lessons (the language didn't get much traction until they added Windows support).
4.10 will also include a recently merged, large change for multicore support: https://github.com/ocaml/ocaml/pull/8713
The plan is to land multicore in trunk through a series of smaller chunks such as #8713
Ocaml multicore has been on the tablet since ... pretty much the dawn of time. It's save to call it vaporware or the duke nukem forever of Ocaml.
> use algebraic effects to compose concurrency and supports parallelism through domains and incremental GC. Rather than adding a specific multicore scheduler into the runtime system, we’re providing the minimum required toolset in the form of pluggable schedulers.
Sure, but at the end of the day what it means is 5 years into the effort OCaml still as limited threading-wise as it was at the start of the effort. And that is what most users (and non-users) care about in a world where 2/4 is your mobile baseline and where AMD's R3-3300G is expected to be 6/12 for $99.
Care to elaborate?