* F5 and A10 front-end traffic management use Tcl at their core -- here's an interesting article from F5 about re-visiting that design decision: https://devcentral.f5.com/articles/irules-concepts-tcl-the-h...
* Tealeaf (http://www-01.ibm.com/software/info/tealeaf/) uses Tcl at the core of its capture appliances.
* Tcl has exceptional testing capabilites -- tcltest drives a lot of the tests for SQLite for example, and is the core of dejagnu, the test harness that drives gcc testing (probably among other things).
* Attempts to replace Tcl at NBC (http://www.researchgate.net/publication/247290458_Prototypin...) have apparently gone on for years -- but nothing has managed to do it.
* Tcl was used in prototyping mars rover work (http://wiki.tcl.tk/13456)
* Tcl is used in chip design (http://wiki.tcl.tk/12897) and other CAD work
* Tcl is at the core of high-end Cisco products... and on and on and on...
I think this[0] really sums up "where is Tcl these days"... it really is out there, if that makes you feel better about using it. If that doesn't matter -- the sheer joy of a solid, battle-tested, fun-to-use language/framework might be enough to draw you in. Try it. You'll like it.
[0] http://www.reddit.com/r/programming/comments/1a1ynm/tcl_the_...
It's a language that deserves better than it got - it should've become the standard for *nix config files (thanks RMS for the mess we have now). It should've been the language Sun pushed to run everywhere (it even supported java-style applets in web pages, without the slow vm startup). It should've filled the Lua niche (to a certain extent it did) as an embeddable scripting language. It should've filled the perl niche - it had good support for invoking external executables in a shell-scripting role, and could even be used as a login shell; it had good regex support, and was a first-class programming language that could be used for web backends. Heck, it even did reactive I/O in the very early days (IIRC there was a fantastic server product that was caught up in the demise of Netscape or AOL or some such) - it should've been Node too. But it always felt a bit unloved at Sun, especially post-Java (and to be fair, who can blame them when Java was that popular?), and it somehow never seemed to reach critical mass.
Don't you like the language (TCL) or the way how GUIs are created? You can also code in C++/Tk for instance.
I'm unfamiliar with the history you're referencing. Was it being anti-executable configs?
I believe you're referring to the ArsDigita Community System, which was written in Tcl, and which ran on top of AOLServer, a web server that supported Tcl as a scripting language.
(ArsDigita's rise and fall was a classic dotcom bubble story, complete with Aeron chairs, fancy cars, greedy VCs, founders with big egos, lawsuits, etc.)
[1] https://en.wikipedia.org/wiki/ArsDigita_Community_System
Tcl is a beautiful language, very easy to learn and very powerful. I remember reading an article by the creator of Tcl where he was amazed that Tcl is used in very different way from what he envisioned. He meant to have Tcl as a glue, high level logic layer, while low level performance-critial stuff would be done in C. That is why Tcl (1) has great support for C and (2) has ugly way of doing arithmetic (e.g. [expr $x + 1]). Truth is that Tcl was never meant to add numbers. But instead people started writing all kinds of software in it, that went far beyond glue layer.
Anyways, yet another great forgotten language.
None of those are legacy projects, but none of them are the primary focus of my work, either.
Not sure if they're 'new' anymore but definitely 'startup'.
I wonder why it isn't more popular.
(I guess this has been at least somewhat remedied in later releases, but that doesn't necessarily have people taking a second look)
FlightAware.com: One of the busiest sites on the Web. Uses Apache/Rivet and a lot of Tcl-based utilities for backend information management.
The funny thing is, that the use of Tcl is explicitly advertised as security through obscurity:
"The combination of AOLserver and the TCL programming language is not commonly found in the Internet, so a potential hacker will need to expend a considerable amount of criminal energy in order to reverse-engineer the application stack." [2].
[1] http://www.project-open.com [2] http://www.project-open.org/en/project_open_architecture
It was made to tie together IC tools after all (at Stanford, if I remember correctly).
And yes, unfortunately the tools end up being old and crufty, and that was my impression of TCL.
I did a bunch of TCL while working at one of the aforementioned companies, and I got to use it enough to see the lisp-y awesome parts (if you squint hard, [ ]s are just oddly shaped parenthesis), and the smalltalk-y stuff, but I still would have preferred using a different scripting language as my interface.