Steadily converting my Bash skills to Tcl.

Downsides so far: low adoption, some awkward quoting rules and process redirection.

Upsides: everything else.

This language is overlooked and "secret weapon"y enough that it could be a good conf talk.
@deech can we bring back Tk as a UI toolkit while you’re at it
@joe unironically, yeah! Now it has theming, a11y screen reader support and single file executable deployment.
@deech it powers Magic and Cadence solvers. Over-represented in Electrical Engineering apparently.
@deech Awkward quoting rules? It's been years since I've looked at TCL but I remember thinking the quoting rules were a little simpler and more uniform than the shell rules. Can you give an example of the awkwardness?
@deech every post of yours about Tcl reminds me of the days when I was coding custom IRC eggdrop bots. Need to find the sources at some point. :)
@deech In my first job, the (Windows-based) app I was working on had an embedded tcl interpreter for UI configuration. I remember porting it from 16bit to 32bit.

@deech the sqlite team are big TCLers as I recall:

https://sqlite.org/tclsqlite.html

The Tcl interface to the SQLite library