Tcl

“both AFAIK have less vulnerabilities than PHP likely thanks to smaller code size”

“the tcl consoles allow you an escape from the cad tool vendor's (usually marginal and restricted) ui”

“The everything is a string approach shows its limits quite quickly.”

“Tcl on its own is good as a configuration language, creating DSLs, or as a scripting/extension interface”

“TCL is the original extension language, and in the very hidebound electronics CAD world, has a very long tail.”

“it shares a lot of the same metaprogramming that Lisps have - more so than the vast majority of other languages”

“I love how everything is a string or can be hacked on a string”

“Tcl always had one foot in the old days and one foot in the modern era”

“Given how stable and clean the Tcl C interface has always been, it's probably a perfect use case for LLM generation.”

“everything else from Java to Tcl to ZFS was a dangerous distraction”

“the only sandboxing that works is default deny, like Tcl or Lua”

“The overhead of using languages compared to the previous is partly why I keep using bash or Tcl.”

“A remarkably comprehensive and well-written introduction to Tcl!”

“TCL doesn't have strong datatypes and that disqualifies it for me”

“But tcl 7.x and before was a pure string-based language. Everything was essentially a eval().”

“I wouldn't necessarily pick it today but it was kind of nice in a way that's unfamiliar to me from modern development.”

“Tcl is pretty good at functional-programming type stuff, and it can absolutely do anything that you could do with a macro.”

“you will be able to do all the same things without drowning in parenthesis and weird syntax”

“tcl requires you to understand mixing 3 different layers of evaluation right off the bat.”

“it is too easy to misuse the quotation rules, leading to subtle bugs”

“it's much cleaner and the "everything is a string"-ness makes sense for a fundamentally text based medium”

“This will run on Windows, Linux, MacOS, and Tcl's starkit/starpack system makes it easy to generate a single executable file”

“it felt very powerful, like Lisp but without the easy syntax”

“Tcl evolved into something quite complex - compiling to bytecode, object oriented features, etc, etc.”

“The objections to tcl I see most often seem to reflect an outdated or incomplete understanding of the language and its capabilities.”

“It can be expressive, redable, sufficiently performant, and makes it easy and fast to develop and test new features”

“Rock solid code, no surprises, was able to handle tens of thousands of concurrent bets.”

“I can't fault that implementation choice when thinking about Tcl as a "Lisp but it's strings"”

“I like tcl as an alternative to shell for any non-trivial scripts.”

“TCL has a lot of options for manipulating strings - take a look at just the built in string command for a start”

“TCL is practically dead, and only lingers on in the EDA industry”

“The tcl model of "everything is a string" makes exactly the right abstraction to create GUI frontends for CLI applications rapidly and keep them simple at the same time.”

“For instance you open a socket, write there any value you have without serialization, read it in the other side, data transfer done.”

“stable, uncomplicated and minimalist tooling that wont evolve out from under you”

“Its simplicity and small size is key, as is its easy integration with C.”

“best thing about TCL is easy syntax and that everything is a string”

“Its simplicity always astounded me since it seems really simplistic but at some level it's just as malleable as lisp.”

“TCL had the ability dynamically load and call into .so's which was really powerful.”

“Tcl got a LOT of traction. Expect was everywhere. Tk kicked ass and took names.”

“Its definitely a great scripting language and is a lot more flexible than it gets credit for.”