News for hackers. Stuff that matters.
Re:Deconstructing the DAO Attack: A Brief Code Tour by astrobe_ on Sunday June 19, 2016 @01:43PM (#11933799)
It's not that it would make sense. It is more like it is the programmer's fault.

Next week's stupid but expensive typo will be received() instead of receive(). What will you demand then? That the compiler refuses names based on the Levenshtein distance?

It's the job of a style checking tool, not the job of the compiler.

Re:Deconstructing the DAO Attack: A Brief Code Tour by kartickv on Sunday June 19, 2016 @11:35PM (#11935902)
That's a false analogy.

Saying it's the programmer's fault is another circular argument. It is, only in languages that make it the programmer's fault, but I would say that it's actually the language designers' fault.