3 ms·
Having a compile fail is catastrophic, not in the sense of the amount of effort it takes to fix, but in the sense that the computer has completely rejected your
by dahart 10y ago
Having a compile fail is catastrophic, not in the sense of the amount of effort it takes to fix, but in the sense that the computer has completely rejected your input. Your compile or execution failed. It won't work without change.
Misspelling English doesn't usually cause a complete failure, or force you to try again, that's my point. The example in the essay was a cute comparison that I think actually is worth considering, but is ultimately comparing apples to oranges.
But, no matter how fast your compiler is, the cost of finding and fixing a mis-spelling in your editor with syntax highlighting is much less expensive than finding them and fixing them with a compiler or by executing the program. Could be a few seconds per typo less expensive, but my professional experience has generally involved builds that take 1-10 minutes. I'll take the syntax highlighting crutch over waiting for my compiler to fail.
- nv-vn 10y agoCompiler errors are much better than the alternative: a run-time bug that won't manifest itself until you put the program under the correct conditions for failure. Compile-time errors are something that programmers have added to compilers to make programming easier/safer because the alternative is truly catastrophic (accidentally shipping broken software and having to isolate more bugs by hand). I'm not really arguing against syntax highlighting, just saying that this argument for it isn't so black-and-white. Keep in mind that there are many issues syntax-highlighting can't catch that your compiler can (unresolved identifiers, using the wrong function, or accidentally choosing the wrong keyword).