{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiebujyaqxkzkvs3ekbvvin7spj7rt4vt674noikiw6on4u4immnke",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjjmseicmp32"
  },
  "path": "/t/why-we-built-a-haskell-package-manager-in-rust/13933#post_8",
  "publishedAt": "2026-04-15T09:02:51.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "I appreciate the sentiment, wanting One Tool to do the job instead of juggling tools.\n\nI didn’t know about the supposed cabal start-up lag, and that is the kind of thing that it would be good to try and reduce down - but instead of abandoning Haskell for it, surely we should work to remove such weaknesses from GHC-compiled programs, and benefit all GHC packages because of it.\n\nMaybe we can extend linear types for in place modifications, or further mature the non-moving GC, or maybe we can replace parts of C internals with oxidised components, but I don’t think a vibe-coded rust replacement for the ecosystem makes sense.\n\nTL;DR is I think there are some interesting ideas, but this project goes about them in the wrong way.",
  "title": "Why We Built a Haskell Package Manager in Rust"
}