Re: [OT] Choosing a scripting language. - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: [OT] Choosing a scripting language.
Date
Msg-id 3F9DE3FB.4090600@commandprompt.com
Whole thread Raw
In response to Re: [OT] Choosing a scripting language.  ("scott.marlowe" <scott.marlowe@ihs.com>)
Responses Re: [OT] Choosing a scripting language.
List pgsql-general
>I agree with you on using the right tool for the job.  Except Perl.
>The more I use other languages, the less I want to use Perl.  Maybe it was
>a bad experience as a junior developer long ago with it or something :-)
>
>
>
The problem with Perl is that it is written to provide any and all ways
to do one thing.
The problem with Python is that it is written to provide on way to do
one thing (in theory).
The problem with this argument is that anybody can be a bad programmer ;)



>---------------------------(end of broadcast)---------------------------
>TIP 7: don't forget to increase your free space map settings
>
>


--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd@commandprompt.com - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org



pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: index question
Next
From: Ron Johnson
Date:
Subject: Re: SCSI vs. IDE performance test