[Rendello]

The trading firm Jane Street is the big OCaml shop, they have a great podcast about all their tech. Each episode is someone from a team talking about the tool they've built, and their whole ecosystem is pretty much bespoke OCaml tooling.

- https://signalsandthreads.com/

(It's one of three programming podcasts I consistently listen to these days, the others being On The Metal and Developer Voices.)

[xedrac]

Bespoke tooling makes me think that the standard tooling is lacking. How does it compare to Rust's tooling?

[no_wizard]

The article isn’t a very technical one. I’d wager when they say tooling they mean any in house program they use as a tool, as opposed to what we as programmers would think of, like compilers, dev tools etc.

Ocaml has a pretty robust ecosystem of good dev tools and build tools.

[Rendello]

If you're talking about me (GP), I meant that Jane Street has built an entire ecosystem around OCaml, from their customer-facing and backend software to traditional OCaml tooling (like build systems). That being said, all I know is from the podcast I linked. I haven't touched OCaml (yet?) myself.

[mbac32768]

lol

imagine everything that's good about Rust tooling but significantly less good or non-existent instead

(the VS Code plugin for OCaml is actually decent though)

[yawaramin]

The VS Code plugin is, like, 90% of the developer experience of most devs. The fact that it's rock-solid in OCaml should automatically bump us up to at least a B grade. Meanwhile the dune build system is powerful and flexible, and compile times are actually blazing fast, unlike Rust's famous slow builds. So yeah, there are pros and cons on each side, I wouldn't say it's a clear win.