And *that* is why static types matter
Sep. 4th, 2015 09:59 pm[For the programmers]
Even today, I often hear programmers complain about statically-typed languages -- that they require planning too much, that you have to deal with compilation, which slows down turnaround. That languages like JavaScript or Ruby or what-have-you are faster to write code. Folks ask why it could be worth slowing down their development. The answer is because it *colossally* improves maintenance.
Today's project was something of an object lesson in programming languages. It was fun, almost an adrenaline rush of hardcore programming. And it wouldn't have been possible in many languages.
( Rewriting the stack in eight hours flat )
Even today, I often hear programmers complain about statically-typed languages -- that they require planning too much, that you have to deal with compilation, which slows down turnaround. That languages like JavaScript or Ruby or what-have-you are faster to write code. Folks ask why it could be worth slowing down their development. The answer is because it *colossally* improves maintenance.
Today's project was something of an object lesson in programming languages. It was fun, almost an adrenaline rush of hardcore programming. And it wouldn't have been possible in many languages.