Xref: utzoo comp.lang.misc:7012 comp.object:2838
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!cs.uoregon.edu!ogicse!zephyr.ens.tek.com!tektronix!percy!data!kend
From: kend@data.UUCP (Ken Dickey)
Newsgroups: comp.lang.misc,comp.object
Subject: Re^2: blip too. [Re: Dynamic typing -- To Have and Have Not ...]
Message-ID: <468@data.UUCP>
Date: 22 Mar 91 16:38:57 GMT
References: <22032@yunexus.YorkU.CA> <11820:Mar1923:59:3591@kramden.acf.nyu.edu> <22075@yunexus.YorkU.CA> <1244:Mar2021:51:4591@kramden.acf.nyu.edu>
Organization: Microcosm, Beaverton, OR
Lines: 21

{Warning: I have not been following this thread}

brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>... Would you write a compressor in a
>dynamically typed language? I wouldn't, because each compile run takes a
>noticeable amount of time, and each test run takes a noticeable amount
>of time. If I used a dynamically typed language, I'd lose big on either
>compile time, run time, or both. That can mean the difference between a
>week and a month in project turnaround time, not to mention a slower
>final program.

Interesting.  I don't know what languages you typically use [Pascal,
Eiffel, C?], but find many more good environments for fast program
development in dynamically typed languages.  If you want fast code,
there are some good Scheme compilers around.

Of course, I write software systems, not just programs.  If you are
doing device drivers, and really require speed, make use of your local
assembler and the hardware caches.

-Ken Dickey			kend@data.uucp