4 ms·
The documentation is stellar and it makes Dream looks accessible even for a non-ML'er like myself. I also liked how you introduced HTML through preprocessing.
by teyc 5y ago
The documentation is stellar and it makes Dream looks accessible even for a non-ML'er like myself. I also liked how you introduced HTML through preprocessing.
I wish F# would take a similar approach. Nothing seems to come close.
OCaml on Windows seem to only run under Msys or cygwin. Do most OCaml devs develop on Linux?
- yawaramin 5y agoOCaml actually runs natively on Windows, it's just that for development some Unix-like environment is needed, because many packages have a habit of accidentally pulling in and using convenient Unix-isms like bash and grep. Nowadays WSL is used by many, and it works great. But the toolchain can produce applications that run on Windows without any special support, and people have been shipping OCaml apps on Windows for a long time. E.g. the Unison file sync utility, the MLDonkey file share program.
- antron-prime 5y agoI do everything under WSL on Windows. So, still effectively Linux :) As for Cygwin, that was my choice for a long time when I started with OCaml. For building fully-native Windows apps, I've used https://fdopen.github.io/opam-repository-mingw/installation/ https://fdopen.github.io/opam-repository-mingw/installation/. However, it still requires a Cygwin environment to run in, because, as yawaramin mentioned, much of the OCaml ecosystem assumes Linux-like tools during build. So, effectively, the Windows setup looks a bit like cross-compilation, where your build environment is Cygwin, but the output is non-Cygwin full-native Windows binaries. The compiler itself and core tools like Dune don't assume Linux tools and are portable. It's many of the packages among the rest of what is there that trigger the Linux tools dependency.