I used to think Tcl was some kind of old losers' scripting language. Every time I saw Tcl used I thought "ugh, you're doing that?". Out of curiosity, I took a look at some Tcl files. They looked like shell scripting to me, and I thought "piece of shit". But I saw a couple of weird hacks, and Wikipediaed it.
For what I saw, it's the most fucked up Lisp. Being based on strings is not bad per se, but then it lacks references and scopes kinda suck save for uplevel. However, that Jim thing could fix most of these issues and end up being quite competent, albeit slow.
Name:
Anonymous2007-05-25 6:45 ID:lzKndGGP
I always thought Tcl was misunderstood. It was never intended for computer professionals to write it, it was for end-users to extend their applications. The same thing Lua could be used for today.
I haven't written much in Tcl, but the ideas behind it appeal to me. 8.5 in particular fixes a lot of the ugly prior versions had (don't need expr for simple math, automatic bigint, Tk with native widgets, "in" for lists, a real dict, inline stack trace, etc, etc).
I don't think I'd try writing anything large in it though. Also, development moves at a glacial pace. :(
Name:
Anonymous2007-05-28 9:20 ID:oxGvWYpb
>>8 has never tried to teach their mother to program. Something I like about Python, its large library, stresses programming newbies out. They're better off with something limited, sure they might reinvent a few wheels but at least they won't give up when confronted with a whole Web site of documentation, rather than a slim book for Lua.
Name:
Anonymous2007-05-28 9:49 ID:nShOU5Qt
>>12
Are you saying that your mother can't program?
Name:
Anonymous2007-05-28 10:26 ID:9yV+Hjdk
>>12
Don't show them the library at first - just stick with basic stuff.