Static typing is security theater for programmers

http://blog.metaobject.com/2014/06/the-safyness-of-static-typing.html
Face it, Haskelitists: There are not a lot of bugs that can be caught by a type system. Such it up and use texting like the rest of us.

>>16
If you ever tried to use a statically-typed language in practice, you wouldn't spew that childish bullshit. Of course the type system can catch only the most trivial errors (like wrong order of arguments or mapping a function over a list twice in two different places), but these trivial errors make up the majority of your day-to-day errors. Static typing points the boring 90% of bugs out for you, so you have more time to think about the non-trivial bugs or flaws in your design.

And static typing is fast. Where with a unityped language you'd have to compile your program, run it, and wait for it to run the whole test suite, a fully statically typed language points out the type errors without even compiling anything! It's these fast turnaround speeds that make static typing so much better for rapid prototyping and refactoring.