Message-ID: <4540FF22.409@commandprompt.com>
Date: Thu, 26 Oct 2006 11:32:02 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
User-Agent: Thunderbird 1.5.0.7 (X11/20060918)
MIME-Version: 1.0
To: mark@mark.mielke.cc
CC: Richard Troy <rtroy@ScienceTools.com>,
	Carlo Stonebanks <stonec.register@sympatico.ca>,
	pgsql-performance@postgresql.org
Subject: Re: OT: TCL vs Perl Re: commit so slow program looks frozen
References: <ehqhpe$20jt$1@news.hub.org>
	<Pine.LNX.4.33.0610261049030.30114-100000@denzel.in>
	<20061026180706.GA14287@mark.mielke.cc>
In-Reply-To: <20061026180706.GA14287@mark.mielke.cc>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


> Perl has a wealth of modules on CPAN to do almost anything you need to.
> TCL has the beginning of one (not as rich), but comes built-in with things
> like event loops, and graphicals (Tk).
> 
> I could go on and on - but I won't, because this is the PostgreSQL
> mailing list. People either get Perl, or TCL, or they don't. More
> people 'get' Perl, because it was marketted better, it's syntax is
> deceivingly comparable to other well known languages, and for the
> longest time, it was much faster than TCL to write (especially when
> using regular expressions) and faster to run.
> 
> Did TCL get treated unfairly as a result? It's a language. Who cares! :-)

You forgot the god of scripting languages, Python... (Yes perl is much
better at system level scripting than Python).

Sincerely,

Joshua D. Drake

> 
> Cheers,
> mark
> 


-- 

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate