I'm a bit confused...

the readme of ocaml-interop says it's "inspired by" ocaml-rs

while ocaml-rs says it "uses ocaml-interop behind the scenes" and "also exports an interop module, which is an alias for ocaml_interop and the two interfaces can be combined if desired"

from a cursory look over ocaml-rs seems possibly the one to use, as the more comprehensive project

The development of the OCaml-Rust interface is a bit organic. `ocaml-interop` aims to be a low-level but safe interface. At Inria we worked with the author to integrate ideas about using Rust's type system to safely work with a GC. We have more ideas to make it better; if someone wants to commit engineering time in this area they should feel encouraged to contact me.

How does it compare to Rust? What do you like about each?

The garbage collector is nice because sometimes you don't want to think about memory management or the borrow checker.

The syntax is really cool, it looks like python but it's completely whitespace insensitive.

The module system is neat, and I actually like writing module interfaces (which are basically analogous to header files in C/C++). It makes dependency injection trivial, because you can have a module say "I depend on a module with this interface, but the caller can choose which one", which is more useful than it sounds.

It's also a functional language, so you have very little mutability, and it supports """monads""" with its super innovative "monadic let" syntax. (It's basically like overloading the semicolon, which probably doesn't make any sense, but it's really cool.)

Dune is a very pleasant build system and Esy is a very pleasant package manager. The language server is good. I'd say in this dimension it's competitive with Rust.

There's really quite a lot to like about OCaml. My biggest gripe with it is no typeclasses/traits. But I have hope that modular implicits will land within our lifetimes.

What exactly is Esy ? I hadn't heard of it before and its website doesn't seem to provide an obvious answer to that question.

You say it is a package manager. Is it supposed to replace opam ? If so what does it offer that opam doesn't ?

It's a package manager that replaces Opam. It doesn't require switches and it caches builds of packages across projects.

It's like Rust's cargo or Elixir's mix. A task runner, mostly.

> The syntax is really cool, it looks like python

I'm squinting really hard but not seeing the resemblance.

I said that because there's no curly braces and you don't usually have to use semicolons

> you don't usually have to use semicolons

That's compensated by the use of double semicolons :O)

Ha! That's only in the REPL, which I never use