4 ms·
Tk is what made people use Tcl, because it was a rare scripting language for GUI on Unix workstations. The Tcl language is actually really clever and interesti
by neilv 4y ago
Tk is what made people use Tcl, because it was a rare scripting language for GUI on Unix workstations.
The Tcl language is actually really clever and interesting, but the textual evaluation model (a much smarter approach than Bourne and C-shell) still made it poor for representing and manipulating graphs.
I was lead for the extension language in a new CASE system, which had rich semantic graphs, including cycles. Tcl ended up being chosen by a cofounder, so I wrote up a doc on language limitations and how to work around them.
(I'd also argued in the early/mid-'90s that the high-level extension language should also be the application implementation language. Such that we'd develop much of the application functionality ourselves in this high-level language, atop a C++ or C core API for foundation that needed that. Python eventually went this route, but hadn't yet. At the time, people in these sectors (which were very different from MIS developers) were thinking of extension language as things customers could use for simple reports or crude customizations or integration glue. Python and Tcl were new candidates for extension languages, and some big-ticket CAD/EDA/publishing tools had already been using their own more powerful Lisp variant implementations.)
- pjmlp 4y agoWe used Tcl back in the day, because of AOLServer, and the startup founders I joined went on to create their own version of the idea. We had Rails and Active Record done in Tcl back in 1998.