I've used OCaml in production for 2 decades without ever needing to use dune, opam etc.
I've used OCaml in production for 2 decades without ever needing to use dune, opam etc.
I will conceed though, the Tarides folks know their shit when it comes to OCaml projects.
The art of writing a reference manual that actually explains how the software works is almost lost, it seems.
The original INRIA docs are also better than the new things on ocaml.org. Literally the only issue with the "old" INRIA pages was the poor quality of the mailing list archive, the rest is great!
I want my tar archives and docs from INRIA. If I was rich, I'd pay for a grant to update the "old" documentation.
I am sure you have specialized needs and find that rpm is best suited for them, although I don't see how opam fails to solve this issue either (anyone can maintain their own opam repository with locked down versions of packages to match exactly what they need to ship to their customers), but that's a separate argument.
For example, avionics systems are developed in a specialized way due to rigorous safety requirements, yet they offer critical global value. They're still specialized requirements though because most software is not developed like that.