[TylerE]

I think you are vastly under-estimating the learning cost. We're talking about teams of developers, not a hobby project. A few months * multiple programmers adds up to man-years really quick.

Go is much simpler. We deployed our first production (admittedly a fairly minor piece) Go service under a week after we made the decision to start using Go.

PS: State is only shared when you make it so. Go concepts like channels make it very easy to write, _and debug_ clear, decoupled non-trivial parallel code.

[Peaker]

If you have to pay the salaries of programmers for the next 3 years to develop some solution, and know that 10% of that time will be spent learning a new technology that will make them 20%-50% more effective for the remaining 90% of the time. Would you do it or avoid it, based on the large cost of 10% of these programmers' time?

[TylerE]

When I have another solution that will make them 30% more effective with only a 1% learning cost, yes!

[Peaker]

I am claiming Haskell will be 20-50% more effective than Go, not than what they're doing now :-)

[TylerE]

Extraordinary claims require at least existant evidence.