Tkinter[0] was apparently released in 1994, so mildly interesting he didn't say "Tcl tends to get ported to weird places like other programming languages."
It's not really ported. tkinter just builds a full Tcl interpreter as a Python extension and passes command strings over to it. This is the use case Tcl was designed for. You can get access to the underlying Tcl instance and issue non-Tk commands.
Technically correct (the best kind of "correct").
My next question to myself was what hardware was running Tcl in c.1997 Cisco equipment? What porting effort was required? I understand there was some proprietary feature work for Cisco IOS, but I don't know what architectural work was required.
Long term, the Cisco router support became the non-recursive execution engine (of Tcl 8.6) which stopped things from blowing up on the tiny stack sizes that Cisco equipment is configured with.
gbacon · · focus · HN ↗
“Tcl tends to get ported to weird places like routers.” (Larry Wall, October 1997)
bch · · focus · HN ↗
[0] <a href="https://grokipedia.com/page/Tkinter" rel="nofollow">https://grokipedia.com/page/Tkinter
kevin_thibedeau · · focus · HN ↗
bch · · focus · HN ↗
My next question to myself was what hardware was running Tcl in c.1997 Cisco equipment? What porting effort was required? I understand there was some proprietary feature work for Cisco IOS, but I don't know what architectural work was required.
dkfellows · · focus · HN ↗
And which gives us tailcalls and coroutines.