3 ms·
I'll say it again every time OCaml is mentioned here: there are programmers who are eagerly awaiting for it to become more friendly to the modern hardware reali
by pdimitar 7y ago
I'll say it again every time OCaml is mentioned here: there are programmers who are eagerly awaiting for it to become more friendly to the modern hardware realities and then they'll use it a lot. Like myself.
(I am mainly waiting for multicore but SIMD/AVX would be nice as well. Transparent parallelization of code without the programmer doing anything about it except supplying a compilation flag would be a game-changer but eh, we can dream right? After all, pure functions can be detected part of the time so I don't see why not.)
I get the vibe that the current community that's driving it forward is small, dedicated and overworked. Sad to hear that but rest assured that the community will grow once OCaml has multicore support. People will want to contribute once they can suddenly replace their Python or Go codebases with OCaml.
(I'd probably also ask to throw away the C strings and only leave the UTF-8 ones in but I am aware that the OCaml developers are very committed to backwards compatibility so likely not going to happen.)
Great work and progress! Keep it up! <3
- Ono-Sendai 7y agoYou may be interested in our functional programming language Winter. It does auto-parallelisation (WIP) and auto-vectorisation: http://forwardscattering.org/post/22 http://forwardscattering.org/post/22 It's not open sourced yet but will be soonish.
- pdimitar 7y agoReally cute. :) Liked the article. That being said, I'm not looking to get back to C++. Your work is interesting though. I'd like to see things like these upstreamed in Rust.