Back in my salad days, I used to write programs for the Wang minicomputer.  The majority of what I wrote was in COBOL (yes, I know).  However, the Wang had a built-in scripting language called “Procedure” that served the same purpose as JCL did on the mainframe IBM’s.  Procedure was powerful enough that you could use it as a batch language, and build applications by gluing together utility programs, similar to what we do with BAT files on the PC.

While Procedure was very simple to use, and made getting certain applications up and running quickly, it had a big drawback: it was dog slow.  So, if it looked like my quick and dirty utility written Procedure was going to be used for a while, I rewrote it in COBOL.  The second writing took a lot longer than the first, but since I’d already proved that the application had significant usefulness, it made sense to rewrite it.

It seems to me that this is a good rule of thumb for modern scripting languages vs. their compiled siblings: Use the scripting languages to try stuff out and come up with something that’s useful. If it looks like the app will be used often, take the time to rewrite it in Java or C# (please, oh please don’t even try to write it in C++).  As I discovered 20 years ago, this approach gets the value you need when you need it.

9/18/2006 8:58:53 AM (Pacific Daylight Time, UTC-07:00)      Comments [0]  development
Tracked by:
http://vionatr.homestead.com/07/eric-hovde.html [Pingback]
http://dujpoet.homestead.com/07/my-black-is-beautiful.html [Pingback]
http://sutropa.homestead.com/01/instructional-design.html [Pingback]