4 ms·

What's wrong with dune? I thought it was really good.

• baby 5y ago
  Horrible doc, the configuration files are a made-up language with no extension, it is completely detached from managing the versions of your dependencies, or their source of origin (package manager? vendored? patched? internal?), horrible CLI, transitive dependencies are imported by default and it's hard to not do that, etc. And then you try to use it in combination with opam and you want to blow your head.
  • LAC-Tech 5y ago
    - thought the docs were good. Same level as cargo or npm or anything else I've used. - the 'made up langauge' is just s-expressions, not any more made up than NPM using a json file. There's no standard file extension for them though, which is fair. - I'll take your word on the rest of them, I didn't do anything heavy duty
    • baby 5y ago
      > - I'll take your word on the rest of them, I didn't do anything heavy duty TBH, that's why you thought the docs were good > - the 'made up langauge' is just s-expressions, not any more made up than NPM using a json file. There's no standard file extension for them though, which is fair. The lack of extension is really the problem, as your editor will not format it or add syntax highlighting. It's very 90's
• yawaramin 5y ago
  detailed answer upthread https://news.ycombinator.com/item?id=31278948 https://news.ycombinator.com/item?id=31278948
• whb07 5y ago
  I concur as well that Dune is lacking. Compared to Rust or NPM. Shoot even dotnet/nugget is significantly ahead of Dune.