kmacy at fsmware.com
Sat Aug 30 16:26:38 PDT 2003
G065363 at xxxxxxxxxxxxxxxxxxxx> <20030830225436.GA1808 at xxxxxxxxxxxxxxxxx>
In-Reply-To: <20030830225436.GA1808 at xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Message-ID: <3f51327e$0$271$415eb37d at xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
X-Trace: 1062285950 crater_reader.dragonflybsd.org 271 220.127.116.11
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:764
> Combine the two, and you have a system that has pretty interesting properties,
> embedded GUI development within a modern OOP enviroment, TK/TCL sucks. Don't
Having used Perl, Tcl, and Python all quite extensively, I have to throw
my weight pretty behind the Python advocates. I believe that Tcl is too
minimal, keeping substantial amounts of state around is rather painful.
In order to get full use of it you really need a number of add-ons
such as incr Tcl and TclX. Python by itself is a much more complete
solution. Until Perl 6 arrives, the one real advantage I see perl as
having is the sheer momentum behind it, both in terms of developers who
know it and the number of modules written for it.
I like the fact that Python has a language definition. Perl's language
definition is the implementation. The only people I know who really
oppose Python are those who have never used it. Some people have a
harder time learning new languages than others. At the university I had
to use at least a half dozen different languages for different purposes,
so I'm not representative. However, I was comfortable writing a 6kloc
application of moderate complexity in it, having never used it before,
after a day or two of writing toy programs in it.
My two cents.
More information about the Kernel