I don't get the Tcl hate. I use it all the time on Cisco gear, and it's incredibly useful. Sure, if you try and turn it into a 10k+ LOC solution, life is going to suck. But in it's use case envelope, so much value.
But then I'm old and still use perl for small stuff, so probably not reading the room....
Time does move on, but not necessarily for good reasons. TCL is the best way to embed programmability into C or C++ code; Oousterhout’s writings on modularity and composability explain why this is so useful to those that lack the experience of winning with it. But we have to use YAML for ops instead and wait for the scarse and slow Go or Java or whatever teams to extend their yaml interpreters every time we need a value to be a loop instead of one value.
>TCL is the best way to embed programmability into C or C++ code
One of the best ways.
See also, Lua.
Last time I checked, embedding Lua in C or C++ was _way_ easier than embedding Tcl
Could you please unpack that? I'm really curious what the differences are.
I am 31 years old and I love Tcl and Perl, and I started my programming journey with C at age 13-14, so I am not sure how old you are! :P