Why not Tcl/Tk?

[Cary O'Brien]

In article <8J2w6.3336$SB2.606281 at ruti.visi.com>,
Grant Edwards <grante at visi.com> wrote:
>In article <4211ctgvusgcma0c6ok1cpmjou98lv9714 at 4ax.com>, Alexander Kluge wrote:
>>-How would you describe the major strengths and flaws of Tcl vs. Python?

[snip]

>
>Tcl 
> Flaws:  
>     Only one data type: string
>     Incomprehensible quoting semantics
>     Roll-your-own control flow
>     No OO support

      can be Slow
      not so good debugging

> Strengths:
>     Tk integration
>     Lots of code out there
>     Roll-your-own control flow

      Event driven programming model.  Makes some 
      network programming much easier.

      Some libraries higher level (i.e. scotty/tnm) and sometimes
      more portable between platforms.

>     
>Python:
> Flaws:
>     No roll-your-own control flow
>     Lots of GUI options
> Strengths:
>     No roll-your-own control flow
>     Good OO support
>     Lots of GUI options
>     Simple syntax and semantics
>     Library modules 
>
>>-Why do you prefer the one you use over the other?
>

I still use Tcl if I am in a hurry to get something working,
but that is changing.

-- c