esy
dune
Our great sponsors
esy | dune | |
---|---|---|
8 | 27 | |
840 | 1,529 | |
0.5% | 1.6% | |
9.2 | 9.9 | |
14 days ago | 6 days ago | |
Reason | OCaml | |
GNU General Public License v3.0 or later | MIT 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.
esy
-
Compiler Development: Rust or OCaml?
As someone who wrote a fair amount of Rust and OCaml code, I have to agree with the author.
While working at Routine (YC W21), I was tasked with porting our core library to iOS to minimize code duplication. This was a lucky opportunity to write something resembling a compiler: it took in schemas described with our in-house data exchange library and generated C (for FFI) and Swift code (for the end-users, i.e., iOS developers).
Since Routine uses OCaml for everything (which was a big motivator for joining the company—I wanted to see how that would work out), I wrote it in OCaml. The end result is a 3-5k LOC project. It's by no means a full compiler, but it was lots of fun to write. The language got in the way incredibly rarely. On average, it made my life a lot easier.
We did encounter our fair share of issues, mostly due to the cross-compilation tooling (we initially used esy [1], flirted with Nix, and eventually switched to opam-cross-ios [2]), third-party libraries, and intricacies of FFI. Those do take their toll on sanity.
[1]: https://github.com/esy/esy/
-
OCaml 5.0 release (including multicore and effects)
What's the current status of Esy? https://github.com/esy/esy
Any plans to backport its design back to Opam?
-
2021 at OCamlPro
It's great to hear that Opam is making progress! I just wished that it would be more deeply integrated with Dune. A package manager that doesn't build is not very useful to be honest. Currently the only way to not have to care about switches and be able to clearly specify dependencies is to use the esy package manager[1] (which had lock files a while ago).
[1]: https://github.com/esy/esy/
-
PR to Merge Multicore OCaml
If you start a project today I would really try to use esy (https://esy.sh/)
I actually don’t use it myself but it seems to bring the modern programming language experience to OCaml
-
Getting Started with OCaml in 2021 · Perpetually Curious Blog
Here is link number 1 - Previous text "esy"
-
Frustrated by lacking cross platform support (hoping to be wrong)
Alternatively, you can use esy.sh for a simpler setup/build process (it does not require running in a Cygwin shell).
-
Opam, PNPM, Node, Esy, Docker, ReactNative on 128GB Mac
Running esy does not work. Apparently, my environment does not know that it is there. Anyone know what is going on here? I have posted this in the discussion for esy@next here. I will get back to you all when I figure this out.
dune
-
Tagging OCaml packages
If you are using the dune build system, add the tag(s) to your dune-project file's package stanza. E.g.:
-
NextJS, the App Router and ReasonReact
One way to get around this is to modify the api/dune file with (include_subdirs qualified); this means that every subdirectory of api/ can be referenced by module namespacing and we don't have to write dune files for every route (or pages) folder. However, the OCaml LSP does not like it and red squiggles will show up in the editor (although the app with still compile without errors). Trying to develop the app knowing those red squiggles cannot be vanquished would drive me nuts, so instead of using (include_subdirs qualified) I just wrote dune files for every route (and page) which gets rid of the red squiggles.
-
Generating .ml test cases from a glob of text files in a directory using dune
2) Neither would having all source/targets specified, as that would entail listing them all in the dune file as wildcard rules is apparently still not a thing: https://github.com/ocaml/dune/issues/307
-
Dune build
There is a small example on the dune home page: https://dune.build/
- The YAML Document from Hell
-
Ask HN: Programs that saved you 100 hours? (2022 edition)
Dune (https://dune.build/) is the preeminent build tool for OCaml development. I don't love its input syntax (s-expressions), and I sometimes miss the ability to write high-level functions to reduce boilerplate (especially for unit tests), but it always gets the dependencies right, and it's fast. This is in stark contrast to some of my experiences with various other build systems, and I am super happy that the default option for OCaml build systems is so good.
- Help getting started with Ocaml
-
Faster Incremental Builds with Dune 3
It's still weird because dune's own site only makes Jane Street references: https://dune.build/.
-
How to print anything in OCaml
ONE of the big benefits of OCaml is its powerful REPL (also called the toplevel), the interactive command-line utility where you can load modules, type in and execute code, and see its results. The modern REPL, utop, has powerful auto-completion and integration with the build system dune, which enables productive workflows like loading an entire project's libraries in the REPL and interactively exploring them.
- Dune 3.2.0
What are some alternatives?
opam - opam is a source-based package manager. It supports multiple simultaneous compiler installations, flexible package constraints, and a Git-friendly development workflow.
statsd-filter-proxy-rs - A filter proxy for StatsD
domainslib - Parallel Programming over Domains
fnm - 🚀 Fast and simple Node.js version manager, built in Rust
ocaml - The core OCaml system: compilers, runtime system, base libraries
eioio - Effects-based direct-style IO for multicore OCaml
CorrinoEngine - CorrinoEngine is an open-source project which will recreate the Emperor : Battle for Dune
proof-systems - The proof systems used by Mina
drom - drom is a wrapper over opam/dune in an attempt to provide a cargo-like user experience. It can be used to create full OCaml projects with sphinx and odoc documentation. It has specific knowledge of Github and will generate files for Github Actions CI and Github pages.
melange - A mixture of tooling combined to produce JavaScript from OCaml & Reason