js_of_ocaml
query-json
js_of_ocaml | query-json | |
---|---|---|
4 | 4 | |
974 | 591 | |
0.9% | - | |
9.8 | 3.8 | |
1 day ago | 10 months ago | |
OCaml | Reason | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
js_of_ocaml
-
Question about the Reason project in general
In reality, most folks that developed BuckleScript frontends with ReasonML switched to ReScript syntax and are happy with it. Some felt more friction because of their reliance on PPXes or FP-heavy libraries (like Relude) and those people tend to use the Melange fork of BuckleScript or they switched to js_of_ocaml.
-
Is there a statically typed functional programming language that doesn't take purity so seriously?
TL;DR: Reason is, and always has been, independent of ReScript (formerly BuckleScript) and is still actively maintained. If you want to use Reason or OCaml to make native code you can. If you want to compile JS from OCaml or Reason you also still can, but you'll want to use either js_of_ocaml or a BuckleScript fork named Melange that was made in response to the BuckleScript/ReScript people's shenanigans. And if you only care about JS-like syntax and JS output, you can use ReScript.
-
Why is Elm more popular than most of its similar alternatives?
Personally, I just use OCaml and compile to JavaScript with Js_of_ocaml. Js_of_ocaml has been stable and actively maintained for a decade, and I don't have to worry if some superficial syntactic change that affects nothing but ASCII art is going to break my code.
-
query-json: A story of cross-compilation with Reason
The compilation to JavaScript is the sweet section of this blog post since we are using OCaml (under the hood while writing Reason), and it allows us to compile directly to JavaScript using js_of_ocaml.
query-json
-
Gojq: Pure Go Implementation of Jq
It's very possible it could be faster; jq seems to actually be fairly unoptimized. This implementation in OCaml was featured on HN a while back and it trashes the original jq in performance: https://github.com/davesnx/query-json
After seeing that one I did my own (less-complete) version in Rust and managed to squeeze out even more performance: https://github.com/brundonsmith/jqr
-
query-json: A story of cross-compilation with Reason
You can see more examples in the parsing tests
What are some alternatives?
melange - A mixture of tooling combined to produce JavaScript from OCaml & Reason
tylr - a tiny tile-based editor
reason - Simple, fast & type safe code that leverages the JavaScript & OCaml ecosystems
yojson - Low-level JSON parsing and pretty-printing library for OCaml
jsoo-react - js_of_ocaml bindings for ReactJS. Based on ReasonReact.
pq - Like jq, but with Python
hashmap - A Golang lock-free thread-safe HashMap optimized for fastest read access.
bs-emotion - BuckleScript bindings to Emotion
relude - FP-inspired prelude/standard library for ReasonML projects
scriptum - No-Frills Functional Programming Lib Augmenting Javascript/Node.js