Re: One language vs. another on the Web...
by "Shaun L. Sides" <arch(at)abts.net>
|
| Date: |
Wed, 15 Mar 2000 08:16:31 -0500 |
| To: |
hwg-languages(at)mail.hwg.org |
| References: |
|
| |
todo: View
Thread,
Original
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 9 Mar 2000, at 10:58, Berk/Devlin wrote:
> 1. Are my fears about scripting languages vs. "real" programming
> languages justified?
IMO, there are quite a few instances in which you can't find
anywhere to draw a line between a scripting language and a "real"
language. Perl, python, tcl, ruby, and several others can all be
used to develop any kind of application you care to name. I think
that maybe the best solution can be to combine interpreted and
compiled languages. Develop in perl, for example, then locate the
bottle-necks and do those sections in C to improve the
performance of the program. There are things you can do with a
line of perl that require pages of C code, which is one of the main
reasons I say this.
As for being left high and dry by the scripting languages . . . I don't
see how. The perl community is established, strong, and vocal,
just to give one example. If Larry Wall pitched his tent tomorrow,
the perl would mourn but keep right on. (I keep using that in my
examples because it's what I'm most familiar with).
> 2. We all agree that developing using a real language will take
> additional time. Are "real" programming languages worth the
> overhead?
See above. ;-)
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2 -- QDPGP 2.61a
Comment: http://community.wow.net/grt/qdpgp.html
iQCVAwUBOM+NLiEw9uEAOtM/AQKATQP7BQb2Kf+xtGjrZpbB+gKcm8FyYFxVlt34
uYpCdCX3vDywF4VK9/GDyXDvjOgjLGHT6R6X7HFLoRMOT2J8MGzvwNh5T0VqWZcI
dmIPC8v/0GNDgrgWOFbw8gnm2o+U1tjfg4vns1kIFDocYWzWxxzp+iVKG+BzTHxA
tF6C5Hp6yoo=
=De6s
-----END PGP SIGNATURE-----
HWG: hwg-languages mailing list archives,
maintained by Webmasters @ IWA
This page is part of a preserved archive of archives.hwg.org. The site is no longer active and its content is not maintained. For enquiries about this archive, write to archive(at)iwanet.org.