Cart
[Home] [By Thread] [By Date] [Recent Entries]
Paul Prescod wrote: > When I am creating new code, dynamic type checking almost always allows > me to be more productive than static type checking. As Jonathan says, > when you are changing or refactoring code, static type checking can more > often catch your mistakes. Since maintenance lasts longer than initial > development this would seem like a clear win for static type-checking > except that it can often bloat and complicate the code and thus provide > more opportunities for bugs to creep in. Another issue (whose important depends on context) is performance. Compilers dealing with static types (whether or not they're safe) can do all sorts of pedal-to-the-metal tricks that are not available in a dynamically typed environment. The performance gain is going to be strongly dependent on the kind of code you're writing, and the importance of the performance gain depends on your business goals. But it's something you don't want to ignore ignore. -Tim
|
