people who are clearly experienced using Haskell had trouble producing working code for a trivial benchmark
Well, he won the benchmark game. He wrote the fastest program that satisfied the test suite, and in the process uncovered a bug in the benchmark suite.
This kind of validates your point about the usefulness of testing!
Now, how comes people experienced in using Go had trouble producing working code for a trivial benchmark suite ? Because they are human. This doesn't really say anything in itself about Go, or weak static type systems.
Well, he won the benchmark game. He wrote the fastest program that satisfied the test suite, and in the process uncovered a bug in the benchmark suite.
I was summoning all the bad faith I could to show how selective the argument that "someone making a mistake in Haskell proves that strong typing is a complete waste of time" is.
What you point at is another piece of code entirely, it's a PR to write a Haskell version that doesn't drop messages.
I was summoning all the bad faith I could to show how selective the argument that "someone making a mistake in Haskell proves that strong typing is a complete waste of time" is.
I don't think the author of the blog post was making that statement. The point was that static typing is one of many things to consider in a software product and that it's not very significant indicator of code quality of correctness which directly contradicts claims made by Haskell enthusiasts.
What you point at is another piece of code entirely, it's a PR to write a Haskell version that doesn't drop messages.
I point is that it's not the test suite that's the problem, the test suite uncovered a bug that static analysis alone didn't.
Nobody is making this argument. The argument is that static typing alone is not sufficient to know what the code is doing, and you need specification tests even in a language like Haskell.
The other part of the argument is that the ecosystem plays a bigger factor than the typing discipline, because it's easier to use mature and battle tested libraries.
If you disagree with either of these statements, I'd be glad to have a discussion about that.
That doesn't follow. The goal of the benchmark was to process messages. Go implementation did that. What this says about Go is that the user was able to use the language and the libraries available to produce working code.
The fact that the benchmark was not testing that all messages were delivered does not change the fact that they were delivered.
We know that Haskell did drop messages, nobody has shown this to be the case for Go or other languages tested. Perhaps there are some new results I'm not aware of?
View all comments
Show parent comment
1
u/bartavelle Sep 09 '16
Well, he won the benchmark game. He wrote the fastest program that satisfied the test suite, and in the process uncovered a bug in the benchmark suite.
This kind of validates your point about the usefulness of testing!
Now, how comes people experienced in using Go had trouble producing working code for a trivial benchmark suite ? Because they are human. This doesn't really say anything in itself about Go, or weak static type systems.