4 ms·
> [...] imagine having them in an automated check list. Buffer overruns, off-by-one errors, uninitialised variables. Already compilers warn you if there's a cha
by tralarpa 8y ago
> [...] imagine having them in an automated check list. Buffer overruns, off-by-one errors, uninitialised variables. Already compilers warn you if there's a chance you used "=" when you meant "==". (If only JavaScript had a way of knowing if you meant "===" instead of "==").
Wait, a compiler that can differ between an assignment and a comparison? Witchcraft! What do those crazy computer scientists invent next? Type checking? Range checks? Testing pre and post conditions?
Fools! Computers will never be able to do that! Academic bullshit!
/s (just in case)
- tralarpa 8y agoTo the downvoter who didn't get the joke: Didn't you notice that the author's examples are exactly those mistakes that a compiler could find? Checklists and unit tests and TDD are useful. But how about first using the right tools? I don't think they tried to repair airplanes with jack-hammers in WWII, so we shouldn't try to program complex systems with Javascript and other low-level languages.