News for hackers. Stuff that matters.
Re:Clojure at a Bank – Moving from Java (2012) by rdtsc on Friday February 27, 2015 @12:33PM (#9120086)
Sounds like you've had a bad experience.

Hopefully they had tests. And unless they've mathematically proved the code always does what it expects (I've only seen that in avionics systems).

Also depends on application of course. Large concurrent and distributed applications benefit a bit less from static typing in traditional languages. Or rather, they are so hard, that type error are not as much of a significance. How concurrency, communication and failure is handled is more critical.

But say a game or a large desktop application with millions of lines of code, could get a larger benefit from static type checking, no doubt.

Now for a bit of personal experience. I have programmed in Java, C#, Python, Erlang, C++. I have found that when working with large or unknown code bases C# for example is great. Just having the IDE and generics support in C# during compile time is awesome. But if I program something from scratch, I can make a lot faster progress in Python. I often put more work into both unit tests and integration tests because I just have more time available.

Also failures during run-time, even in Python, in my systems a very rarely type errors (those are caught pretty early one). But they are often logic or concurrency errors.

There are no comments on this comment yet.