News for hackers. Stuff that matters.
Re:Static Typing Where Possible, Dynamic Typing When Needed ... by mannykannot on Saturday August 05, 2017 @02:46PM (#14937228)
> Static typing provides a false sense of safety, since it can only prove the absence of certain errors statically.

That is as blatant a straw man as I have seen recently. I have never met someone who mistook static types for a guarantee of correctness, though I have met several people who did not understand why testing to 100% statement coverage does not do that.

The authors would be well-advised to remove this sort of thing if they want to be taken seriously, and in general, striving to "do our best to make it provocative" is not an effective way to influence people, no matter how smart it makes you feel.

Re:Static Typing Where Possible, Dynamic Typing When Needed ... by astrange on Saturday August 05, 2017 @07:56PM (#14938757)
I constantly see people discuss Haskell as if it prevented you from writing incorrect programs. But in fact static typing as it’s usually implemented does nothing for numeric programs/math errors. It won’t even catch dividing by 0.

Related: saying a program is correct because it’s been “security audited” (someone read the source once) or “formally verified” (someone wrote the program twice and didn’t make any typos).

Re:Static Typing Where Possible, Dynamic Typing When Needed ... by mannykannot on Saturday August 05, 2017 @09:02PM (#14939073)
Your dismissive characterizations of security auditing and formal verification are way off the mark.