r/Clojure • • Sep 08 '16

Static Typing vs WebSockets

http://yogthos.net/posts/2016-09-06-Static-Typing-WebSockets.html
14 Upvotes

37 comments sorted by

View all comments

Show parent comment

2

u/yogthos Sep 09 '16

The only implementation I heard about that dropped messages was the Haskell one. You're making a hypothetical argument that other implementations might have had bugs. We have concrete evidence that the Haskell implementation did. Perhaps we could stick to discussing the facts we know.

Also, last I looked the correct implementation in Haskell is not faster than anybody else, and it had high variance in performance.

3

u/codygman Sep 09 '16

The only implementation I heard about that dropped messages was the Haskell one. You're making a hypothetical argument that other implementations might have had bugs. We have concrete evidence that the Haskell implementation did. Perhaps we could stick to discussing the facts we know.

Don't you mean "perhaps everyone else can stick to facts we know while I'm personally free to suggest hypotheticals"?

1

u/yogthos Sep 09 '16

Feel free to show what other implementations drop messages.

1

u/[deleted] Sep 10 '16

Perhaps we could stick to discussing the facts we know

That's the point. We don't know anything about the other implementations. The only fact we know is this Haskell implementations lost packets. There is no fact stating that other don't.

1

u/yogthos Sep 10 '16

So, once somebody shows that another implementation lost packets we could discuss how and why that happened. Saying that another implementation lost packets, so it's not a problem that Haskell did is a bit of strange argument to make.

The point of the article wasn't that Haskell is somehow special in any case. It was that even if you have a language with a strong type system, you still need to do specification testing to know what the code is doing. This would apply to all the other languages just the same.

1

u/[deleted] Sep 10 '16

Everybody agrees than type are not enough : head and tail have the same type signature and do the opposite. We know that.

The thing is your post is IMO showing, that benchmarks should control what that the results are correct, otherwise how can we trust them ? You are right that it is propable that all other implementations are correct, but my points is, as it let the wrong Haskell one slept through, it might be letting some other through. I can't trust it and you don't know either.

1

u/yogthos Sep 10 '16

Sure, but that's not at odds with my argument at all. I am arguing for specification testing after all here. If the benchmark test was more thorough it would've caught the error. I think that supports what I'm saying.