Why We Use OCaml
I don&#x27;t know if it brings anything new on the table. Also, I am not convinced that Ocaml is state-of-the-art in term of development productivity, relase-management, debugging, etc. Anything any non-trivial project could want. Language features is not the only thing we need.<p>Yes, the OCaml tooling has really improved recently, and the OCaml workflow has been more and more smoother. Still. I wont recommend it for a business.<p>So, if the original author read this, could you answer these questions about <i>how</i> do you ship products with Ocaml:<p>- How do you do Quality Assurance ? (anything from unit-testing, integration testing, functional testing, etc. I guess you have to do it a lot to check that Gmail didn&#x27;t break its integration). Testing in isolation has its share of challenges in Ocaml.<p>- How do you manage your builds and releases ? Private Opam repositories ? Directly shipped to Google ? Do you have beta&#x2F;staging channels ?<p>- And last but not least, what have been the pain points so far and have you been able to fix them or do you just work with it ? (it happens with any tech stack, but it&#x27;s good to know what the trade-off are)<p>I am very curious how this could work at &quot;entreprise-scale&quot; and I would be glad to have some real world examples of ocaml in production.