A really bad bug. It’s nice to see both how quickly it was handled, and how polite the bug report was. Given the potential severity of deleting a user’s ~/.ssh folder, I’m surprised the reporter wasn’t irate.
Just goes to show the importance of backups. Or managing the contents of ~/.ssh in some other method that can restore things when needed.
I’m a little bit put-off by how quickly the Haskell community moved to stack. Cabal had its problems (and stack hasn’t replaced cabal so much as it lives on top of it) but I felt like people were too quick to deprecate vanilla cabal and push stack when it didn’t seem that the kinks had been worked out.
The thing I love about Haskell is the ability to write extremely reliable code. Unfortunately, I found that a number of things I wanted to do were stack-reliant because the community had jumped to the new solution so quickly, and I found stack to be changing so quickly that the installation process didn’t always match what was said in the resources.
All of that said, this is a minor criticism and I’ll give the Haskell community this: they do care about correctness and technical excellence (and, alas, most of the software industry doesn’t) and they’re quick to fix bugs, especially nasty ones like this.
Spin up enough new people/projects and you start to really appreciate Stack for how much time it saves you. Kick around one of a few projects on the reg and it seems less compelling.
Becomes more so if you change compilers between projects or within the same project.
That makes a lot of sense. It’s obvious even now that Stack is better than vanilla Cabal. The trouble I ran into with it was also months ago, and it seems to have improved a lot.