testcross
Re:Melange 1.0: Compile OCaml / ReasonML to JavaScript
on Monday June 12, 2023 @09:12PM (#36303814)
on any decent size application the output of bucklescript/rescript/melange is also unreadable. I never understood that argument.
some real problems with jsoo are (non exhaustive list)
- "heavy" FFI (both in term of setup and syntax)
- the output is a big single .js file, which doesn't allow reloading of a single component and doesn't integrate well with stuff like webpack
- slower compilation time
- lacking documentation for the javascript audience
Re:Human-like neural network chess engine trained on lichess games
on Tuesday January 19, 2021 @05:56PM (#25840081)
https://en.wikipedia.org/wiki/TCEC_Season_19
stockfish finished +9 over 100 games.
I don't have any stock in those 2 engines, so I don't care which one is better than the other. At the end as a poor chess player it won't change anything :) It's actually interesting to compare how those two software are evolving and how they got here.
Stockfish is much older. And it took it a lot of hand tuning to reach its current level. It is (or was) full of carefully tested heuristic to give a direction to the computation. It would be very difficult to build an engine like stockfish in a short span.
Leela got there very very quickly. Even if it was not able to win in October, the fact that it got competitive and forced the field to adopt drastic changes in such a short period of time is impressive. It seems to be a good example of how sometimes no using the "best" solution could still be a win. Getting good results after a few months against something that required 10 years of work.
Re:Human-like neural network chess engine trained on lichess games
on Sunday January 17, 2021 @08:26PM (#25817201)
Actually stockfish crushed leela in recent TCEC. It seems that the new neural network of stockfish had a huge effect on the performances. Something like a 130 ELO improvement.
Re:ReScript 8.4
on Tuesday December 15, 2020 @09:34AM (#25430652)
I don’t see how there’s a biased intent. I’ve no shares in any tech. If anything I wish for rescript to be a big success given how much the company I am in relies on it. I’ve contributed to multiple bucklescript projects. And I’m not criticising the decisions of anyone.
Re:ReScript 8.4
on Tuesday December 15, 2020 @03:45AM (#25428306)
well sorry if this isn't true, but I haven't insulted anyone. If I get those feedback and they are incorrect, I hope that you can provide my insightful ones to clear the situation.
Re:ReScript 8.4
on Tuesday December 15, 2020 @03:43AM (#25428294)
Btw for people who want to use js_of_ocaml instead of rescript but still like react, there is https://github.com/jchavarri/jsoo-react. It's obviously not as polished. But it's interesting to see how much work it requires to bind a large lib like react.
Re:ReScript 8.4
on Tuesday December 15, 2020 @03:13AM (#25428146)
I feel like the dev team is using "readable output" to mean both "human-readable" and "shared data types" depending on the situation. And it creates a lot of confusion.
Re:ReScript 8.4
on Tuesday December 15, 2020 @02:49AM (#25428003)
actually bucklescript has never really been used at bloomberg. And bob left bloomberg a long time ago. So this fork is definitely not happening because of bloomberg.
To have code that you can compile to both native and js, the easiest thing is to stick to the ocaml syntax. It is supported by all the versions of the compiler (rescript or ocaml). And to also use the ocaml syntax for the tools doing code generation, such as atdgen.
Re:ReScript 8.4
on Tuesday December 15, 2020 @02:46AM (#25427986)
from what I heard, they use typescript instead of reason for some time already. I don't know if they use react or not. I also heard that they weren't always using reasonreact even when they were using reason. So they've never been 100% on the same stack than what was advertised by the reason team.
It probably explain why fb dedicates so little resources to reason too.
Re:ReScript 8.4
on Tuesday December 15, 2020 @02:43AM (#25427977)
from the feedback I got, they migrated to something else
Re:ReScript 8.4
on Tuesday December 15, 2020 @01:07AM (#25427503)
actually I think that it is basically not used inside facebook anymore. But it is used in a bunch of other companies.
Re:Reparse – A comprehensive parser combinator for OCaml
on Friday December 04, 2020 @07:30AM (#25301535)
the author wasn't aware of angstrom or other alternatives.
OCaml User Survey 2020 Results
Re:Compiler for the M language of the French DGFiP
on Friday October 09, 2020 @12:31PM (#24731583)
The author explains what were the challenging bits in this thread (in french): https://twitter.com/DMerigoux/status/1314531302079688709
Compiler for the M language of the French DGFiP
State of the Shell: PowerShell7
From rescript to JS_of_OCaml, a case study with vscode-OCaml-platform
Re:Teardown of the Singaporean Covid-19 TraceTogether Token
on Friday June 26, 2020 @01:58AM (#23649141)
https://xobs.io/trace-together-token-teardown/ has more details
Teardown of the Singaporean Covid-19 TraceTogether Token
Diffwhat: List all functions affected by code changed in a commit
An in-depth look at OCaml’s new “best-fit” garbage collector strategy
Animal Crossing Tune Maker
Procedural World Generation of Ubisoft’s Far Cry 5
Quick Reference and Starter Exercises for Learning Coq
Paredit/smartparens for all languages and editors using tree-sitter?
There was a recent post on /r/emacs about bindings to tree-sitter: https://www.reddit.com/r/emacs/comments/chnxzm/dynamic_module_binding_for_treesitter_an/I don't know all the internals and features of tree-sitter, but I wonder if it could be used to create a paredit or smartparens mode which would work on all languages and respect their semantic. Ideally it wouldn't even have to be emacs...