On the latter front that jvm work is a summer of code student. So on one hand it's definitely exciting work, there's definitely a bit of work between that .. Working and it being a tier one backend for ghc.
I've been haskellin at a large Megacorp environment for the past 1.5 years, with lots of smaller freelance before that.
There's a lot of different value props one can make for different tools. One pragmatic case I make is that in Haskell land it's super easy and rewarding to to engage with upstream to resolve any problems I hit. One other angle that the imvu article and I think a lot of the comments over look is that using Haskell as a shared concrete specification / engineering design substrate for communicating actually makes it much much easier to collab with colleagues on pretty crazy projects. Even if the deployed system isn't ultimately written in Haskell.
That said, with the right colleagues, having the freedom / trust to choose tools that help you best deliver is always the ideal. :)
I've been haskellin at a large Megacorp environment for the past 1.5 years, with lots of smaller freelance before that.
There's a lot of different value props one can make for different tools. One pragmatic case I make is that in Haskell land it's super easy and rewarding to to engage with upstream to resolve any problems I hit. One other angle that the imvu article and I think a lot of the comments over look is that using Haskell as a shared concrete specification / engineering design substrate for communicating actually makes it much much easier to collab with colleagues on pretty crazy projects. Even if the deployed system isn't ultimately written in Haskell.
That said, with the right colleagues, having the freedom / trust to choose tools that help you best deliver is always the ideal. :)