On Tue, 4 Jan 2000, Brad 'GreyBear' Davis wrote:
> As for how to do DB connectivity I don't think you necessarily have to use
> Perl at all, although it's a cool language. It depends a lot on who needs to
> access the DB, where they need access and whether you always need or even
> want a GUI to the DB. We're developing a Perl interface to PostgreSQL for
> our backend web processing of orders, but I'll probably develop a web/native
> interface to the DB so regular mortals can add items to the DB using a
> friendly easy to use app to do so.
I love Perl, so don't think I'm super biased towards Java or something (or
though it does have it's place like most things).
This sounds like duplicated work. If you are going to write some in Java,
then run Java servlets and reuse the code - as long as you write it
properly you can easily seperate the GUI code from the DB logic. You can
also put a Tk front end to perl and reuse code that way. I wouldn't use
both if there is any overlap in functionality.
>
> If you do C++ you'll do fine with either Java or Perl. The right tool for
> the right job is the important thing, IMHO. I went the other way, learned C,
> skipped C++ and went straight to Perl and finally Java. They finally made me
> do OOP anyway... #8^D
He, I've seen lots of pretty good C++ programmers not at all comfortable
with perl, so i don't think that's necessarily true. I totally agree about
C++ --> Java though. Piece of cake. Also please don't forget that as long
as you are not anal retentive and can see past things like enforced data
privacy, you can also write lovely object oriented Perl too, and enjoy all
the features of oop. In fact half the time people are writing perl they
are using objects and don't even know it. :)
Oh, and perl has more than sufficient DB access libs to do your e-commerce
website, so don't let that be a deciding factor to go to Java.
charles
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
