Re:Why Don't Software Developers Use Static Analysis Tools t...
by crdoconnor on Friday June 26, 2015 @07:10AM
(#9783527)
>Java code does tend to be much less buggy when compared with dynamic-typed code
I only see this happen when both the Java code and the dynamically typed code both have zero tests.
IME, once you actually start taking integration testing seriously and actually exercise your code even just a little, the benefits of static typing evaporate pretty quickly.
Re:Why Don't Software Developers Use Static Analysis Tools t...
by raz32dust on Friday June 26, 2015 @07:35AM
(#9783605)
Then you indirectly agree that java code requires less tests, which means static typing helps!
Re:Why Don't Software Developers Use Static Analysis Tools t...
by crdoconnor on Friday June 26, 2015 @08:31AM
(#9783845)
Nope. The same tests you'd need anyhow to catch logic errors will end up catching type errors.
If a test becomes unnecessary if you have static typing then you should never have written it in the first place. It's a bad test.
Re:Why Don't Software Developers Use Static Analysis Tools t...
by dllthomas on Sunday June 28, 2015 @03:28PM
(#9794714)
"If a test becomes unnecessary if you have static typing then you should never have written it in the first place. It's a bad test."
That seems a very strong - and unsupported - claim. Could you elaborate?
I have no stats here (and neither do you :)), but based on my experience, Java code does tend to be much less buggy when compared with dynamic-typed code, keeping the features and quality of developers the same. Of course, logical bugs don't get caught by static typing. But it helps a lot when refactoring code, or collaborating on the same codebase with many people, or changing someone else's code. These things become really important once the code base hits a certain size.