Proponents of Tcl consider it a versatile, feature-rich, industrial strength programming language. It is renowned for its stability and utility. Tcl is used for for everything from quick systems administrative scripts to mission-critical control systems. It is simple to learn, and fun to use. This page enumerates the advantages and strengths of this unique language and provides an index of other resources that do the same.
see Who Uses Tcl
pidors 2005-01-20: I just saw 10 Things I Hate About tcl show up in http://del.icio.us/tag/tcl . Would it be worthwhile to address his list? (though it is from Oct 2004, so one might consider it a stale part of the blogoverse). :)
George Peter Staplin: It seems to me that most of the arguments in that article could be solved by studying Tcl.n.
It seems that the author hasn't used programming languages unlike C. To find syntax errors before runtime execution we have tools such as frink. The delayed-evaluation/syntax-checking isn't a problem in most cases for me. I have, however, wanted the ability to fix the problem in a dialog (during the error) and continue execution after the change (like in Smalltalk, and Lisp), but this would require many changes to Tcl. Furthermore, regarding syntax analysis; I've written plenty of buggy programs that pass a C compiler's checks. Depending on a compiler to find bugs in a program can be a futile pursuit.
Caj: When I evangelize Tcl, the number one argument I make is its complementary nature: it is excellent at precisely those things you hate to do in C, and writing in both languages together is really easy. Every coder at some point stares resignedly at a source file thinking, "I wish I could just write this part in perl." Tcl is a cure for exactly that writers block.
Joe Mistachkin 2006-06-08: Based on my previous research (when I had access to the actual hardware), modern versions of Tcl have not been ported to HP MPE/ix. Please correct me if this is inaccurate.
Here are some big companies that have used Tcl successfully:
There are several success stories available at the Tcl Developer's Exchange website http://www.tcl.tk/about/audience.html
Don't just defend Tcl, promote it!
peterc 2008-08-19: Another practical way to increase the visibility of Tcl is to suggest modern and current Tcl books to your University library for purchase. Most will not only purchase the books, but, will also put them prominently on display in their foyer for the book's first few weeks in the collection.
So you get 'em with "eye-share" at the point of entry for a few weeks, then have crisp and modern-looking textbooks available on the shelf for the browsers later on.
LV There is a directory entry for Tcl and Tk at http://directory.fsf.org/project/tclTk/ - the FSF directory of free software. However, the entry is 3 years old, refers to 8.5 alpha, makes references to the source being maintained on sourceforge, etc. Someone with time to spend advocating Tcl in the public eye might consider tracking down the process of updating that page, updating this note to add that discovery, and then submit an update bringing the information up to date.
MG can't claim to have a lot of time to spend advocating Tcl, but has registered on the FSF site and filed a bug report that the page is out of date, which appears to be the way to get it updated.
See also the About Tcl/Tk pages on www.tcl.tk http://www.tcl.tk/about/
If you're like most technical people, you're unclear just how management make decisions on what software is used for a project. At times they seem like a black box into which good advice goes and from which bad decisions emerge. The Linux community has put together some good information on how you can sell management on Tcl (of course, they're telling you how to get Linux accepted, but in most cases the ideas and approaches are the same).
Does it frustrate you to have people saying things about Tcl that you know are untrue, but which are hard to refute on the spot? Here's our cheat sheet for Refuting Common Myths About Tcl:
On the other hand, be certain that you check the license of any extensions, tools, or distributions that you use during development. Just because Tcl and Tk are free doesn't mean that everything in the community is free.
George Peter Staplin: (adds) You should also have firmly in your mind why Tcl is better. Blind faith is like no faith at all.
EKB A little story: I took this advice, but with unknown results! There was a discussion thread [L3 ] on Joel on Software titled "Cross-platform GUI dilemma". The poster described his problem as, "I have a low-level back-end thing that is written in C. I have a command-line shell for it that I wrote as a debugging tool. It's working pretty well and I would like to wrap it in a GUI so I can demo it to nontechnical people. I would like to support Windows, Linux, and Mac if possible." This seemed like a no-brainer, but no one had yet recommended Tcl/Tk and far down the thread there was a post, " geez, this all sounds so complex...wx this and Gtk that and , holy cow...You guys discourage development - I must say, it makes me glad to have my Visual Studio - and now I know why I stick to Windows development lol" Yikes! So I added a post at the end, "You can use Tcl/Tk, then wrap it into a Starkit or with Freewrap for a standalone executable. Tcl/Tk is *great* for wrapping a command-line app in a GUI. Info is available at [...link to Tcler's Wiki...]" After that there was a great, thundering silence, and after a longer time the thread was closed and archived. I got the last word, but I don't know that anyone heard...
See: http://discuss.joelonsoftware.com/default.asp?design.4.108173.51
Ulrich Albrecht One more story, same implication: A couple of years ago I was working at the technical university of Aachen (Germany) on a robot simulation and path-planning system, including fast collision detection. The core functionality was included in a C++ class hierarchy describing robot parts and kinematics, with a lot of C libraries from other sources mixed in. The code was to perform on a real robot controller (a PPC-machine running vxworks), SGI Irix (MIPS), Sun Solaris (SPARC), Linux (Intel) and eventually MS Windows (Intel), so we could not include any platform specific stuff. With the exception of vxworks though - where the real thing was moving - we thought we should have a GUI with a virtualization and visualization of the robot and its environment. Tcl/Tk looked good, because it was the only package that was as portable, flexible and extensible as we needed. I wrote an OpenGL-widget for Tk and a Tcl-to-C++ command-wrapper for every C++ class I needed to construct and control at runtime, and ended up with a robotics-enabled wish I could feed all kinds of szenarios and interact with. I can really say that 1. portability was not a big issue, because the core C/C++-libraries were OS-independent and Tcl/Tk as well as OpenGL were properly ported, 2. performance wasn't either, because the critical parts were nice, dirty compiled C/C++, 3. usability was very good because of the robust interactive Tcl-interpreter we could use for free, 4. the Tk-part performed and looked a lot better and more OS-consistent than anything I've since seen in Java...
We even run this stuff in MS Internet Explorer (using the Tk-Plugin) for demonstration purposes.
Nearly forgot: Porting the code to MS Windows was not the problem - it was the makefiles that nearly drove us mad.
Notice the essay on language selection Kevin Walzer mentions.
http://www.businessweek.com/magazine/content/05_05/b3918001_mz001.htm
Nice article about the success of Linux. It discusses how they have successfully navigated the waters between wild and wooley RMS radicalism, and corporate giants like IBM, and how Linux is on a roll that doesn't look to stop anytime soon. - davidw
HJG Many things can be done in Tcl/Tk much easier than in other languages. I think we need a page for a list / showcase of such programs.
LV: A co-worker, after reading a recent Regular Expressions column by Cameron Laird, had this to say:
For those upon whom this comparison is lost, see:
http://www.ruf.rice.edu/~bioslabs/studies/mitochondria/mitorigin.html
...or an earlier take on the Tcl/Tk-mitochondria analogy, and the "symbio-friendliness" of Tcl/Tk:
Lars H: I suspect that co-worker would lose sleep if all mitochondria disappeared, since these supply most of a cell's energy (anything that consumes oxygen; when the mitochondria can't keep up, you get lactic acid). I wonder what the computer analogue would be. The Internet crashing because all the routers with embedded Tcl would stop functioning if it suddenly disappeared? Hmm... perhaps the analogue works, after all!
aa: I think you misread the intent of the comment. The idea of Tcl/Tk/mitochondria going away isn't a cause for worry. Not because it would be a benign event if they did, but simply because they're not going to go away.
Think of all the programming languages of the world as a forest. Tcl is a clearing in the middle of the forest where the sun shines, a cool breeze blows, and you can get a breath of fresh air.
You might be lost if you've not been to the clearing before, but it's real easy to find your way around. Just don't expect as many things to be laying on the ground waiting to trip you up.
Oh, and you can make your own trees. -- (Bryan Oakley on comp.lang.tcl, 2007-07-12)