I guess it depends on your expectations. I'm working on a ~38000 SLOC Haskell program (an optimising compiler: http://futhark-lang.org), and with GHC 8.0.1, a full build takes about 7 minutes. I can cut off a minute or two by passing `--fast` to Stack. However, even small incremental builds take a significant amount of time due to linking, which is what annoys me the most. It's still far from making me disavow Haskell, but it's definitely not among the fastest-compilable languages.

This program is also too big to load in GHCi, at least on my laptop with 8GiB of memory.

No, it's a very common issue brought up within the community that GHC takes a lot of time and memory.

That blog post just says that interpreting Haskell can be faster than compiling.

I worked with Haskell professionally on a pretty large codebase. It was split up into many separate libraries and binaries. There were a lot of coffee breaks when recompiling.

https://www.reddit.com/r/haskell/comments/45q90s/is_anything...

That feels like a limited optimization in the context of practical development.