Tom Hacohen has been writing software program for 20 years, over time he’s grown sure that robust static typing is “not simply a good suggestion, but additionally nearly all the time the best selection.”
Discover the hedge in that sentence? “Virtually all the time” is the best way individuals discuss after they’ve been writing software program for a very long time. After laying out his exceptions, Tom goes on to state his case:
“would you slightly work a bit extra and get invariants checked at compile-time (or type-checking time for non-compiled languages), or work a bit much less and have them be enforced at runtime, and even worse not enforced even at runtime (JavaScript, I’m you…). Getting errors at runtime is a horrible concept. First, it implies that you received’t all the time catch them throughout growth. Second, once you do catch them, it can occur in a buyer dealing with method. Sure, checks assist, however writing checks for each potential mistyped perform parameter is inconceivable given the infinite prospects. Even in case you might, having varieties is far simpler than testing for mistaken varieties.”
His overarching factors are {that a}) varieties result in much less bugs, and b) varieties result in a greater developer expertise. And the cash quote:
“Writing software program with out varieties helps you to go at full velocity. Full velocity in the direction of the cliff.”
