Hacker News Reader

Comment by Joel_Mckay | Hacker News Reader

TCL is popular for automated scripting, and is still quite popular with "expect" and "autoexpect" package users. The key feature is opening a remote scripted or interactive ssh session, and running setup/install commands admins would otherwise have to type in thousands of times a month (or worse, leave sensitive information/CSR on short lived host nodes.)

Being able to compile ephemeral objects is actually pretty useful in some use-cases. =3

View on HN

Not contributing much to the discussion, but thanks for explaining who still uses Tcl. It was my first programming language about 20 years ago (I used it to write scripts for Eggdrop - an IRC bot). Just stopped by the comments out of nostalgia.

The language core is still actively used, but not in the way most people assume.

Expanding TCL C support proves it is not deprecated as some suggested (most Java VM also run a dual stack with C/C++ native binary object support.)

Automated remote host administration with TCL is one area where it still works extremely well... I guess it is not relevant if people like pseudo-repetitive typing... so much typing people actually know all the parameters to tar without the manual. lol

Have a great day =3

Nitpick: it is Tcl, not TCL, just like how Ada is not ADA.

Following the Wikipedia citation will point people here:

https://wiki.tcl-lang.org/page/Tcl+vs%2E+TCL

Which gets into the syntactical preference people developed over time.

The Tool Command Language acronym allusion is rather distinct from a popular "Tcl" colloquialism for the "tickle" project. From my perspective Tcl is a TCL, but not all TCLs are necessarily Tcl nor include a specific extension package.

Have a glorious day friend =3

When I say it out loud, I say T-C-L, too, but I write it as Tcl.

You have a nice day too! =3

Reply on news.ycombinator.com