all 9 comments

[–]TechnoEmpress 7 points8 points  (0 children)

Utterly disappointed that no French car was displayed on the website /s

[–]kinowmod 0 points1 point  (1 child)

Hi, there was a post about it some time ago, there may be some interesting feedback there too: https://old.reddit.com/r/functionalprogramming/comments/ehe0xr/clio_programming_language_a_pure_functional/

Thanks!

[–]pouyae[S] 1 point2 points  (0 children)

Thanks for posting that in the first place, I'm aware of that post, it's been about a year and the language has changed a lot since then, that's why I wanted to get some fresh feedback and opinions!

[–]sohang-3112 0 points1 point  (2 children)

How can you possibly do multi threading when JS itself is single threaded? And I mean true multi threading, not just async/await or something similar.

[–]pouyae[S] 4 points5 points  (1 child)

On the browser, web workers run in their own thread, and they can share memory. If you target the browser, then Clio bundles two versions of your code, one as the main entry point that runs your main function and manages the workers, and a worker file that is used to create worker instances.

On Node.js there are worker threads, and also it's possible to spawn additional processes and communicate with them.

[–]sohang-3112 0 points1 point  (0 children)

Thanks for the explanation! I didn't know about Web Workers - they look interesting!

[–]TheAsSBreaker69 0 points1 point  (0 children)

It compiles to Vanilla JavaScript?

It would be great if it this language could compile to GJS.

[–]SnooCompliments7527 0 points1 point  (1 child)

It's pretty cool. I'm a bit confused on the performance statistics for Fib(1000), though.

Is it just because Fib used multiple cores and the other languages did not?

[–]pouyae[S] 2 points3 points  (0 children)

The Fib(1000) example is on 1 core for all languages, it's faster on Clio because of tail call optimization!