Why We Built a Haskell Package Manager in Rust

I appreciate the sentiment, wanting One Tool to do the job instead of juggling tools. I 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. Maybe 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. TL;DR is I think there are some interesting ideas, but this project goes about them in the wrong way.