🚀 go-pugleaf

In article <gperkinsDn90ww.Gu4@netcom.com>,
Glen C. Perkins <gperkins@netcom.com> wrote:
 >Jonathan Scott Duff <duff@cbi.tamucc.edu> writes:
 >
 >>Glen C. Perkins wrote:
 >>> 
 >>> opinions, fight it out. The result has been a significant
 >>> expansion in the number of languages I use, rather than
 >>> just using C for everything. (Actually, the truth is,
 >>> it has expanded my repertoire enough that I *never* use
 >>> C for *anything* anymore!)
 >>>
 >
 >>Hmm... Why do you never use C anymore?  It sounds like you
 >>are fanaticizing over languages instead of just using the
 >>right one for whatever job you have at hand.
 >
 >I don't use C anymore because I don't have any problems
 >that C handles better than Perl or Java or Lisp or
 >Delphi (which is for the whole system, not the Pascal.)

Makes sense. It sounds like you just aren't writing system-level code that also
needs to be portable.

If you decided to, say, write a ray tracer or a little OS kernel, you might
want to migrate back to C. :)

 >If I wrote drivers or spreadsheet recalc engines, I'd
 >use C. I don't. I use Java for web applets, Perl for
 >CGI and local file processing utilities, Lisp for genetic
 >algorithms experiments, and Delphi for commercial windows
 >apps (series of vertical market products).
 >
 >Thanks to the availability of these wonderful tools, I
 >don't use C for anything anymore. Are these the rantings
 >of a "fanatic"? You be the judge....  ;-)

Not at all. If you did want to write drivers or "recalc engines", you'd be back
in C in a jiffy. Or just write code that is portable to systems that aren't
blessed with Delphi support from Boreland.
--