cabal hell isn't even a real thing anymore.....
replyI know that. Bumping GHC can still be relatively painful. Some language stacks are meaningfully easier on dependencies (not you Python), but can give you some other headaches (yes, you Python, damn you). Every PL in one way or another has some warts and ugly parts.
replyIt seems the job of a senior software engineer these days is to make fun of programming languages on HN pointing out their flaws, while simultaneously keeping an eye, waiting on agents doing "thinking".
whoa buddy, i'm a senior eng but i don't wait on agents. ew!
replyi could probably do my job and get passing (or better) perf reviews using nothing but fundamental-mode and the compiler.
I only use Haskell in hobby projects outside of work but somewhat regularly run into problems with package bounds causing conflicts or forcing some project on to an older GHC than I'd like. It's not cabal hell since its confined to one project and not system wide, but it's definitely a pain point.
replyso Go has the same issues in my experience. but instead of "solver failed" you get compilation errors. I definitely had to fork a nontrivial amount of Go libraries to maintain my startup's backend.
reply"solver failed" is in theory a better error. it fails faster and is unambiguous. maybe because it's weird it is scarier? idk
the main issue is managing PVP bounds is a little hard to keep correct. but cabal also lets you "allow-newer" for duct tape.