[lmm]

> I bet I can find 10 succeeding that use ruby or node for everyone that uses Erlang.

But that's not the question, is it? There are a lot of companies succeeding with ruby or node, but also a lot of companies failing with them. I'll bet the strike rate is better for Erlang companies.

[jshen]

Il bet that the choice of language has no impact on success.

[codygman]

What about whitespace? Do you think choosing it or brainfuck has an impact on success?

[jshen]

Not relevant. I'm sure there are bad choices, but the difference between Go and Haskell is probably negligible or in Go's favor.

[lmm]

So you think Go is a better language because companies that use Go are more likely to be successful because... Go is a better language? That's just circular reasoning. Do you have any numbers or experience here?

(In my limited experience I've seen a 100% success rate for companies that use Haskell and a 0% success rate for companies that use Go, though as you can imagine I don't have a statistically valid sample size)

[jshen]

Right, there is no good data at all suggesting that languages like Haskell are better for teams. Yet we are constantly served peoples overly confident opinions that they are.

[tome]

We are? Links please.

[codygman]

As someone with experience in both languages I disagree. Try parsing json in both languages and you'll see a difference. Composing functions that use channels simply isn't possible in Go (please prove me wrong).

Go gives you kind of safe concurrency, Haskell gives you actual safe concurrency.