{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreian2dbowedfp6363x2ts7w7ue2fkzn7ldl3digupcsjygilvqettu",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjjg3gghs5d2"
  },
  "path": "/t/why-we-built-a-haskell-package-manager-in-rust/13933#post_5",
  "publishedAt": "2026-04-15T06:25:33.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "I read the article, but I do not understand what they are trying to achieve.\n\nIt seems like a thin wrapper around various tools, so that I only ever have to interface with one cli app.\n\nThere’s some confusing optimization claims, e.g. they circumvent cabal when there are only boot dependencies (probably just running `ghc --make`). How does that even work with cabal.project files?\n\nNow there’s also yet another custom config format, which seems to rather add to the fragmentation than remove it.",
  "title": "Why We Built a Haskell Package Manager in Rust"
}