As worth studying as any language is. I think Tcl is really neat and would like to use it more at work, but most software comes with Python API's now, so there

As worth studying as any language is. I think Tcl is really neat and would like to use it more at work, but most software comes with Python API's now, so there is an advantage to popularity. Also, Python has the scientific libraries I need without needing to drop down to C with Tcl. Your mileage may vary. I've used a bit of Tcl for some simple things, but Windows isn't exactly a first class citizen and I don't like how the various distributions of Tcl seem a bit less trustworthy than just downloading a Python distribution from the python or anaconda (scientific distribution) websites. After reading Ashok Nadkarni's book though, I decided I felt the Tcl design was more coherent to me in a lot of ways. The way it sticks so heavily to commands is very consistent, but languages like Python (or something like APL that goes to the absolute extremes) use special syntax to make certain things easier to recall (think of how Tcl uses "lindex" for accessing arrays and Python has dedicated "array[4]" syntax. Neither is better than the other, just different. Tcl to me is a lot like a Lisp built off of strings rather than lists. Many on HN will point to how this is inferior, but the overall language and ecosystem has been a lot easier for me to pickup. Edit: I have nearly a decade of regular Python usage under my built for things like process automation and a little scientific computing, but have only read a book on Tcl, read blog posts, and coded a little bit every now and then.