Sure, I find that with cabal and/or stack you often have to do things like manually add/link files for compilation and also both go mod and cargo support pulling libraries directly from Github say easily (using something like GO_PRIVATE), which I think is possible in cabal but you have to use project files which I never found intuitive. Also, just by virtue of having a smaller user base obviously the package ecosystem is smaller (this isnt the fault of the tooling) but in practice it means that community IDE plugins for things like autochecking for updates just aren't as good for Haskell.
The things above are definitely a skill issue on my part, I'm sure all of this is possible with cabal and stack and I may just not be using them right, but I definitely found cargo and go mod to be a lot simpler to get started with. Also, for cross-compilation and for FFI I found cabal to be a pain when including C sources where as Go was trivial through CGO (and the tooling around it was too).
Sure, I find that with cabal and/or stack you often have to do things like manually add/link files for compilation and also both go mod and cargo support pulling libraries directly from Github say easily (using something like GO_PRIVATE), which I think is possible in cabal but you have to use project files which I never found intuitive. Also, just by virtue of having a smaller user base obviously the package ecosystem is smaller (this isnt the fault of the tooling) but in practice it means that community IDE plugins for things like autochecking for updates just aren't as good for Haskell.
The things above are definitely a skill issue on my part, I'm sure all of this is possible with cabal and stack and I may just not be using them right, but I definitely found cargo and go mod to be a lot simpler to get started with. Also, for cross-compilation and for FFI I found cabal to be a pain when including C sources where as Go was trivial through CGO (and the tooling around it was too).
I love Haskell though so all good <3