The Tcl ecosystem is so diverse that it's hard to characterize it, but it divides roughly into two camps. On the one hand are the Tk enthusiasts who believe that the Tcl/Tk's main contribution is its powerful cross-platform GUI tools; they think of Tcl/Tk as a stand-alone programming platform, and are constantly pushing for more Tk features. On the other hand are the Tcl purists who believe the most unique thing about Tcl is that it can be embedded into applications. This group is most interested in the simplicity and power of the APIs for embedding. The Tcl purists worry that the Tk enthusiasts will bloat the system to the point where it will no longer be embeddable.
What is Tcl’s relevance in the web application world?
What was the flagship application made with Tcl?
Tcl's strength has been the breadth of activities that it covers, rather than a single flagship application. Most Tcl applications are probably small ones used by a single person or group. At the same time, there are many large applications that have been built with Tcl, including the NBC broadcast control system, numerous applications in the Electronic Design Automation space, test harnesses for network routers and switches, Mars lander software, and the control system for oil platforms in the Gulf of Mexico.
Unfortunately I don't know very much about those projects, and the information I have is pretty old (I heard about both of those projects in the late 1990s). For the oil platform project, I believe that Tcl/Tk provided the central management system for observing the overall operation of the platform and controlling its functions. In the case of the Mars lander, I believe Tcl was used for pre-launch testing of the system hardware and software.
Have you ever seen the language used in a way that wasn't originally intended?
The most surprising thing to me was that people built large programs with Tcl. I designed the language as a command-line tool and expected that it would be used only for very short programs: perhaps a few dozen lines at most. When I went to the first Tcl workshop and heard that a multi-billion-dollar oil platform was being controlled by a half million lines of Tcl code I almost fell over.
Were there any particularly difficult or frustrating problems you had to overcome in the development of the language?
One problem we worked on for many years was making Tcl and Tk run on platforms other than Unix. This was eventually successful, but the differences between Unix, Windows, and the Macintosh were large enough that it took a long time to get it all right. A second problem was language speed. Originally Tcl was completely interpreted: every command was reparsed from a string every time it was executed. Of course, this was fairly inefficient. Eventually, Brian Lewis created a bytecode compiler for Tcl that provided 5-10x speedups.
Can you attribute any of Tcl’s popularity to the Tk framework?
Absolutely. As I mentioned earlier, there are many people who use Tcl exclusively for Tk.
Generally, more and more and more coding is moving to scripting languages. What do you think about this trend given Tcl’s long scripting language heritage? Has Tcl gained from this trend?
I think this trend makes perfect sense. Scripting languages make it substantially easier to build and maintain certain classes of applications, such as those that do a lot of string processing and those that must integrate a variety of different components and services. For example, most Web applications are built with scripting languages these days.
Looking back, is there anything you would change in the language’s development?
Yes, two things. First, I wish I had known that people would write large programs in Tcl; if I had, I'm sure I would have done some things differently in the design of the language. Second, I wish I had included object-oriented programming facilities in the language. I resisted this for a long time, and in retrospect I was wrong. It would have been easy to incorporate nice object-oriented facilities in Tcl if I had done it early on. Right now there are several Tcl extensions that provide OO facilities but there is not one "standard" that is part of Tcl; this is a weakness relative to other scripting languages.
Where do you envisage Tcl’s future lying?
Tcl is more than 20 years old now (hard to believe!) so it is pretty mature; I don't expect to see any shocking new developments around Tcl or Tk. I'm sure that Tcl and Tk will continue to be used for a variety of applications.