3 ms·
I work at one of the largest Haskell-in-production companies in the world There are issues outside of the actual authorship of code you need to take into accou
by gavinray 4y ago
I work at one of the largest Haskell-in-production companies in the world
There are issues outside of the actual authorship of code you need to take into account if you want to choose Haskell. I'll leave it at that.
It's a fantastic language undoubtedly.
But if you've never experienced the maintenance and upgrade of a very large Haskell codebase over a period of years, especially if you have a big dependency-tree, and need to interface with external tools (database drivers, etc.) I'd urge you to talk to someone who has for a view into the experience. Also ask about the state of things like profiling and compiler bugs/memory leaks.
EDIT: I want to note that the state the general Haskell ecosystem/tooling has improved at a dramatic pace in the last ~3-4 years, with the advent of HLS and recent GHC releases.
- jackmott42 4y agoYeah an important lesson for programmers is that for big projects the ecosystem around a language is usually more important, for any given metric (productivity, quality, performance), than the language itself. Python being used to do high performance math all the time is a good example of this. Python the language isn't at all good at that, but the ecosystem has nice libraries with high performance C code underneath them. If one comes to believe there is a language that really is a lot better, then you have to get to work building out the ecosystem around it to realize that, and it isn't easy!