7 ms·
Two reasons: it was targeted as an embeddable application extension language (kinda like Python); and, thanks to Tk, it was a relatively easy way to make passab
by neilv 6y ago
Two reasons: it was targeted as an embeddable application extension language (kinda like Python); and, thanks to Tk, it was a relatively easy way to make passable GUI interfaces on Unixes.
(There was also a very brief attempt early in the Web to use Tcl for Web development, as an arguably superior alternative to then-popular things like Perl CGI, but that didn't take over.)
What people should've been using for embeddable extension languages is a Scheme implementation, which, besides other merits, wasn't crippled by an evaluation model based on string expansion. I was in charge of one such extension language for a system that cost 5 figures a seat, and Tcl's string evaluation wasn't that up to representing objects and graph references well. (At the time, extension languages of major applications were often some simple/custom Lisp.)
Tcl was pretty neat, in how much more clever it was about some kinds of string evaluation than Unix shells, but a Scheme would've still been a better choice.
- gnufx 6y agoTCL is fat,slow,and lacks staying power. — (SIOD author) George Carrette, 1994 At least we could direct people who wouldn't see the light towards Python at that stage.