News for hackers. Stuff that matters.
Re:Clojure at a Bank – Moving from Java (2012) by liviu- on Friday February 27, 2015 @09:38AM (#9119006)
>I also dispute the claim that a strong type system is a "tiny factor" in code quality.

There actually are some studies that show that using a static typing system is only a tiny factor when it comes to code quality:

http://wadler.blogspot.co.uk/2011/09/experiment-about-static...

However, I've also read studies that show the opposite, but the lack of rigurosity and the possible confounds that show up for both sides seems to render this as an open question.

Re:Clojure at a Bank – Moving from Java (2012) by mercurial on Friday February 27, 2015 @10:02AM (#9119167)
> However, I've also read studies that show the opposite, but the lack of rigurosity and the possible confounds that show up for both sides seems to render this as an open question.

This doesn't look particularly convincing, indeed (though studies about programming languages rarely are).

Re:Clojure at a Bank – Moving from Java (2012) by calibraxis on Friday February 27, 2015 @09:46AM (#9119061)
With Clojure, you can begin to compare static vs. dynamic typing — keeping the language the same.
Re:Clojure at a Bank – Moving from Java (2012) by Glide on Friday February 27, 2015 @10:36AM (#9119373)
A language having static or dynamic typing is only a part of the puzzle. Having tools that let you understand a codebase better through static typing is more important. With a statically typed language you have the compiler as a baseline, but it enables IDEs to do far more powerful things.