Tcl, short for Tool Command Language and pronounced "tickle", was created by John Ousterhout at the University of California, Berkeley, starting in 1988. He wanted one small interpreter that any program could embed instead of inventing its own clumsy command syntax. The key decision, and the answer to why everything is a string in Tcl, follows from that goal: if every value is a string, any C program can pass data to the interpreter and back without negotiating types.
Origins at Berkeley
Ousterhout's group built interactive tools for integrated circuit design, including the Magic VLSI layout editor. Each tool needed a command language, and each one ended up with a weak, half-finished one. Around the winter of 1987–88 he decided to write a reusable interpreter as a C library. Tcl was presented publicly at the USENIX Winter Conference in 1990, and by then it was already spreading across Unix labs.
The companion GUI toolkit, Tk, followed soon after and was publicly available by 1991. Tcl/Tk made it possible to build an X11 window with buttons in a dozen lines, at a time when Motif programming took hundreds. That alone won Tcl a large audience.
Sun Microsystems hired Ousterhout in 1994 to push Tcl further. In 1998 he left to found Scriptics (later Ajuba Solutions), and in 2000 stewardship passed to the community-run Tcl Core Team. Tcl/Tk received the ACM Software System Award in 1997.
Why everything is a string in Tcl
Tcl's grammar fits on a page; the official rules are known as the "Dodekalogue". A script is a sequence of commands, each command is a list of words, and the first word names the command. Square brackets run a nested command and substitute its result, $ substitutes a variable, and braces quote text without substitution. Even if, while and proc are ordinary commands that receive strings, so you can write your own control structures.
Treating all data as strings made embedding trivial and the language extremely regular, but early versions paid for it in speed, re-parsing numbers on every use. Tcl 8.0 (1997) fixed most of that with a bytecode compiler and a dual-representation Tcl_Obj: a value keeps a cached internal form, such as an integer or list, while still behaving as a string whenever you look at it.
A short Tcl example
proc greet {name {greeting "Hello"}} {
return "$greeting, $name!"
}
set langs 1,740 sites · page 19 of 35Website IP Address Submit Website Featured 91.108.119.105 Claude Featured Not updated yet Semrush Featured Not updated yet Tech Bullion Not updated yet TechGig Not updated yet The Good Men Project Not updated yet The Odyssey Online Not updated yet Thrive Global Not updated yet TradingView Ideas Not updated yet TravelBlog Not updated yet Triond Not updated yet Twoday Not updated yet TypePad Not updated yet UberArticles Not updated yet uCoz Not updated yet Vocal Media Not updated yet Web-Source Not updated yet Webflow Not updated yet Webnode Not updated yet Webstarts Not updated yet Weebly Not updated yet Wikidot Not updated yet Wix Not updated yet WordPress.com Not updated yet Xing Not updated yet Xomba Not updated yet Yola Not updated yet Yumpu Not updated yet Zenodo Not updated yet 118000 Not updated yet 11870 Not updated yet 118712 Not updated yet 11880 Not updated yet 11890 Not updated yet 118Information Not updated yet 123Achei Not updated yet 1Businessworld Not updated yet 2Cu Not updated yet 2Findlocal Not updated yet 40Billion Not updated yet 411 Not updated yet Aaspaas Not updated yet Aboutus Not updated yet Abqfind Not updated yet Abr Not updated yet Achecerto Not updated yet Addonbiz Not updated yet Addsera Not updated yet Addyp Not updated yet Adnify Not updated yet Adoak Not updated yet Adsansar Not updated yet Agentlocal Not updated yet
✓ Links verified Oct 24, 2026
foreach lang $langs {
puts [greet $lang]
}
puts [string length "everything is a string"]Note that the list built by list is still a string you could print, split or store in a file, then read back as a list later.
Where Tcl is used today
Tcl is less visible than Python, but it is deeply embedded in some industries:
- Electronic design automation: tools from Synopsys, Cadence, Siemens EDA and Xilinx/AMD use Tcl as their scripting interface, so chip designers write Tcl daily.
- Networking: Cisco IOS includes a Tcl shell, and F5's iRules for BIG-IP load balancers are written in a Tcl dialect.
- Expect, written by Don Libes at NIST around 1990, automates interactive programs such as
ssh,ftpandpasswd. - Tkinter, Python's standard GUI library, is a wrapper around Tcl/Tk, so every Python installation with Tkinter carries a Tcl interpreter.
- Web servers such as AOLserver and its successor NaviServer, plus testing frameworks like DejaGnu and the SQLite test suite.
Versions timeline
| Year | Release | Notable change |
|---|---|---|
| 1988 | First versions | Embeddable interpreter at Berkeley |
| 1997 | Tcl 8.0 | Bytecode compiler, Tcl_Obj |
| 1999 | Tcl 8.1 | Unicode strings, threads |
| 2007 | Tcl 8.5 | Dictionaries, argument expansion, ttk themed widgets |
| 2012 | Tcl 8.6 | TclOO, coroutines, non-recursive engine |
| 2024 | Tcl 9.0 | 64-bit sizes, full Unicode range |
Influence and legacy
Tcl had a famous critic: Richard Stallman's 1994 Usenet post "Why you should not use Tcl" set off the so-called Tcl War and helped push GNU toward Guile. Ousterhout answered with a broader argument, later published in IEEE Computer in 1998 as "Scripting: Higher Level Programming for the 21st Century", which made the case that scripting languages and system languages serve different jobs. That essay is still cited in discussions of language design.
Tcl's idea of an embeddable, tiny interpreter set the pattern Lua later perfected, and its event loop and fileevent model predated the async style that became popular decades later. If you want to understand why everything is a string in Tcl, think of it as a design for glue: strings are the one format every program already understands.
Frequently asked questions
Does everything being a string make Tcl slow?
Not much since Tcl 8.0. Values keep a cached internal representation, so an integer stays an integer until you treat it as text. Tcl compiles procedures to bytecode, which puts it roughly in the same performance range as other classic interpreted scripting languages.
Why do chip design tools still use Tcl?
EDA vendors adopted Tcl in the 1990s because it was easy to embed in large C and C++ applications. Decades of design flows, scripts and training are now written in it. Switching would break customer workflows, so Tcl remains the standard command interface.
Is Tkinter in Python really Tcl?
Yes. Tkinter loads a real Tcl interpreter and sends it Tk commands behind the scenes. That is why Python distributions bundle Tcl/Tk libraries, and why Tkinter errors sometimes mention Tcl.
