News for hackers. Stuff that matters.
Re:Announcing Rust 1.20 by amelius on Friday September 01, 2017 @04:48AM (#15147036)
Doesn't ANY rewrite (regardless of whether there is a change in language) reduce bug-count, simply because all the requirements are more clear in advance and the engineers have had more time to think about a suitable architecture?
Re:Announcing Rust 1.20 by lomnakkus on Friday September 01, 2017 @05:25AM (#15147145)
Nope. Churn (= number of lines changed) is actually pretty well correlated with bug count.

I don't have a precise reference off-hand, but I believe I read it in "Making Software: What Really Works, and Why We Believe It".

Obviously you'll probably get closer to what the software is intended to do, but it probably won't reduce bug count in the short term. In the long term, you might end up with fewer lines of code overall (which is also correlated with overall bug count).

Re:Announcing Rust 1.20 by amelius on Friday September 01, 2017 @05:44AM (#15147203)
> Churn (= number of lines changed) is actually pretty well correlated with bug count.

Is a rewrite considered as bunch of line changes or not? I would say not.

Also, can I assume that by "correlated with" you mean "positively correlated with"?

If so, isn't a rewrite reducing bug count because you'll end up with far fewer "changed" lines?

Re:Announcing Rust 1.20 by lomnakkus on Friday September 01, 2017 @07:09AM (#15147460)
I would assume a rewrite counts as a bunch of line changes -- absent evidence to the contrary. Obviously, if you're changing the language that changes the equation, some bugs which can happen in C++ simply cannot happen in Rust, for example.

(And yes, I meant "positively correlated with".)