🚀 go-pugleaf

c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku) writes:

>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.

Right.

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

Right again. Unless I felt *really* ambitious and decided to do
it in assembler (at least the stuff inside the loops.)

I don't have any such projects, so I don't use C for anything.

> >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.
>-- 

Right.

At the moment, though, I'm busy dreaming of a day when I can
write Java apps and implement the classes in any language I
want (say 80% Java and 20% Perl for my needs), compile them
all into the same Java bytecode and, thanks to just-in-time
compilers that execute code so fast it bends the laws of physics,
have it all execute as fast as if I'd written it all in C.

Of course, by that time, Latte will have blown the doors off
Delphi and Visual Basic in terms of ease with which professional-
looking apps can be "laid out" (versus "programmed")...   ;-)

__Glen Perkins__

-- 
+---------------------------------------------------------------------------+