Friday, May 09, 2003

Strong Typing vs. Strong Testing. In recent years my primary interest has become programmer productivity. Programmer cycles are expensive, CPU cycles are cheap, and I believe that we should no longer pay for the latter with the former. [Thinking About Computing] Excellent article by Bruce Eckel on Strong vs. Dynamic Typing. He gives his examples in Java vs. Python. Bruce contributes to the growing sentiment that compilation checking in statically typed languages is really just a small number of tests. To determine if code is really correct, then you have to use unit tests. If you are using unit tests for your dynamically typed code, there is no reason it won't be just as correct as your statically typed code. Plus, dynamic languages are usually much easier to work with! Great praise for Python in this article. 8:54:41 PM    comment []

Language Fermentation. If you're a programmer, I think you're lucky, because this is an exciting time we're living in: there's some powerful intellectual ferment in progress out there. This may be the golden age of programming, as Paul Graham argues, and maybe everything we thought we knew about strong typing is wrong. Herewith a bit of surveyware with a touch of debunking and a practical footnote on Java exception handling. (Warning: geeky.)... [ongoing] Great thoughts on Strong vs. Dynamic Typing. A really clever use of Java's RuntimeException - to eliminate throwing exceptions throughout your code. 8:29:09 PM    comment []

© Copyright 2004 Tom Pierce.