4 ms·
Still waiting for Duke Nukem Forever, aka multicore, until then OCaml has major limitations for such a low-level and performance-oriented language.
by aaron-lebo 9y ago
Still waiting for Duke Nukem Forever, aka multicore, until then OCaml has major limitations for such a low-level and performance-oriented language.
- yawaramin 9y agoLet's be honest. You don't really need multicore (i.e. language-level parallelism support) for most enterprise work. Hence people use NodeJS just fine. OCaml has not one but two very nice concurrency libraries so for most backend work you will be absolutely fine.
- Can_Not 9y agoSure, but for specific projects, I'd leave NodeJS faster if OCaml had multicore.
- yawaramin 9y agoYou don't even need to leave NodeJS to get all the OCaml benefits: BuckleScript compiles to readable JS. Compare the input and output of the example: https://github.com/bucklescript/bucklescript#an-http-server https://github.com/bucklescript/bucklescript#an-http-server You can get all the type safety benefits of OCaml right now, on NodeJS.