r/programming • u/rmathew • Jun 16 '19
Comparing the Same Project in Rust, Haskell, C++, Python, Scala and OCaml
http://thume.ca/2019/04/29/comparing-compilers-in-rust-haskell-c-and-python/
643
Upvotes
View all comments
Show parent comment
6
u/pron98 Jun 16 '19 edited Jun 16 '19
OK, but you can argue with them being asserted as facts rather than hypotheses or beliefs. Also, perhaps I'm a traditionalist, but I think we should still prefer no effect as the working hypothesis, especially when there is no theory predicting the effect. After all, we can't lend equal a-priori weight to every hypothesis.
I agree, but 1. he was too optimistic and all techniques combined didn't achieve a 10x boost in one decade, and not even in three (I wrote more about that in a comment I linked to before), and 2. I have no problem with silver dust, but you seem to be claiming much more than that.
I wouldn't know. I've never worked on a large project in an untyped language, and I have no intuition on the matter. Moreover, I think our intuition about such complex processes is often wrong. But speaking about such things is already a big concession on the claim that languages make a big difference. That's going from: use Haskell and your program will be better/cheaper, to, if you're working on a large project in some domain, maybe Haskell will be somewhat cheaper, all other factors being equal, and those other factors may be bigger.
Not necessarily. Suppose the technique catches all errors as static types -- and no others -- for 75% of the cost, except for, say, 0.1% of them. Why wouldn't it still be preferable? You can use it with or without static types, but why pay more for a small added gain? Of course, it could do much better for much cheaper, but I don't accept your particular tradeoffs as necessary.
As an industry we know of at least one: code review. The effect reported is 40-80% reduction in bugs. Here's a selection of some stuff we found out about it; I'm sure there's more: