THC: Tight Home Control, automation framework in Tcl

Re:THC: Tight Home Control, automation framework in Tcl by na85 on Tuesday July 27, 2021 @12:09PM (#27974107)

Wow, I have always been dubious of the claim that Tcl continues to be used in "behind the scenes" applications today. For a long time it was just (for me, anyways) That Thing You Have To Learn To Script Your Eggdrop Bot but it's a neat albeit quirky little language and evidently is used in at least this project!

Kudos!

[ Parent | on HN ]

Re:THC: Tight Home Control, automation framework in Tcl by SwSwinger on Tuesday July 27, 2021 @12:52PM (#27974625)

TCL is quasi-religious. You either appreciate the simplicity and elegance of the 12 clearly ordered rules, or you think the nutbag scruffie programmer is talking to a burning bush.

I learned TCL for adding an embedded scripting language to a company's command line in 2005. I originally cast derision, but have learned to appreciate its beauty after a wrote a couple API frameworks in it. I think it has a little less magic now that lambdas and other shorthand notations are commonplace.

[ Parent | on HN ]

Re:THC: Tight Home Control, automation framework in Tcl by AceJohnny2 on Tuesday July 27, 2021 @03:27PM (#27976479)

Another anecdote: the MacPorts package definition files [1] are actually TCL programs. MacPorts itself is built on TCL [2]

[1] Example portfile: https://github.com/macports/macports-ports/blob/master/shell...

[2] Macports source: https://github.com/macports/macports-base/tree/release-2.7/s...

[ Parent | on HN ]

Re:THC: Tight Home Control, automation framework in Tcl by flopp on Tuesday July 27, 2021 @03:06PM (#27976238)

It's still highly used in the EDA industry - almost every EDA tool is scriptable with Tcl. There are even IEEE formats that are actually Tcl dialects, e.g. UPF (Unified Power Format) for describing power related features of circuits.

[ Parent | on HN ]

Re:THC: Tight Home Control, automation framework in Tcl by dexterhaslem on Tuesday July 27, 2021 @12:26PM (#27974299)

once you recognize it, you may start to catch it in use in applications all over the place. if you ever use xilinx tools, ECAD, etc, you will see reams of tcl handling builds and project definitions

[ Parent | on HN ]

Re:THC: Tight Home Control, automation framework in Tcl by Brian_K_White on Tuesday July 27, 2021 @02:22PM (#27975711)

This is a blast from the past. All the SCO Open Server 5 sys admin tools are tcl, both the curses and gui front ends. I haven't touched it since then. I had no strong opinion about it either way at the time.

[ Parent | on HN ]

Re:THC: Tight Home Control, automation framework in Tcl by na85 on Tuesday July 27, 2021 @12:31PM (#27974372)

My impression was that Tcl used to be very popular for that sort of thing, but that it was supplanted by Lua, Python, and JavaScript.

What makes Tcl compelling for those applications?

[ Parent | on HN ]

Re:THC: Tight Home Control, automation framework in Tcl by buescher on Tuesday July 27, 2021 @01:58PM (#27975453)

Network effects. John Ousterhout invented tcl in part to script/implement the Magic VLSI layout tool. So it's not surprising it's spread to other EDA applications.

[ Parent | on HN ]

Re:THC: Tight Home Control, automation framework in Tcl by dexterhaslem on Tuesday July 27, 2021 @12:46PM (#27974558)

that I couldn't tell you. I'd personally pick lua (or damn near anything else) first. maybe just entrenched knowledge/tooling in certain industries monster codebases.

[ Parent | on HN ]

Re:THC: Tight Home Control, automation framework in Tcl by RHSeeger on Tuesday July 27, 2021 @12:56PM (#27974676)

Personally, I'd pick Tcl long before Lua... but I'd pick almost anything before Lua; which I find frustrating to work with. There's a _lot_ of personal preference and "feeling" that goes into what each person likes in a language.

[ Parent | on HN ]

Re:THC: Tight Home Control, automation framework in Tcl by kjs3 on Tuesday July 27, 2021 @01:55PM (#27975430)

Also, Cisco IOS scripting.

[ Parent | on HN ]