Personal opinion: Tcl was lots of fun and somewhat unique in being both a convenient scripting language and an easily embeddable language. But in the end Python and Lua became better replacements for those two specific areas (that's at least how it went in my case, I did lots of Tcl in the late 90's and early 2ks, but then switched to Python for "cross-platform-scripting").

There's still no proper replacement for Tk GUIs as far as I'm aware though, even Python uses it for building quick'n'dirty cross-platform UIs.

> but then switched to Python for "cross-platform-scripting").

For simple scripting I've switched to Powershell (formerly Windows PowerShell). It's OSS, you can use it from the command line and it's available on Windows/OS X/Linux.

https://github.com/PowerShell/PowerShell

Not sure why you are being downvoted, you aren't wrong.

How does it compare to Python?

Powershell can be pretty expressive.

It has a lot in common with Python, but the syntax is more C like when you're scripting, but can be used like a standard shell as well.

The learning curve is partially steep as it takes time to learn the advantages and complexity of piping objects around instead of text streams (like Linux does).

The major deal breaker for me is that file reads and writes which are glacially slow. Like waayyy slower than Python if you can believe it even if you basically call the .NET libraries directly instead of the cmdlets.

So it makes the most sense for Windows IT admin tasks.

The syntax is uglier, and it doesn't have anything like PyCharm. However, as a shell it's syntax lends itself to typing out on the command line. It does have this weird thing where you use lots of aliases to make things ergonomic on the command line, but tend to use the full name in the script. Example "ls" is "Get-Child-Item" and is usable on more than just directories.

What sets it apart IMHO is that it return records instead of just string so you can declare which fields you are interested in instead of trying to parse the string output with "cut"

Tcl is still fun :) We use it at work as an embedded language. It powers many features, and is a quite large part of our product.

It has absolutely lost some mindshare, but I still think it's a great choice.

same here. In the hardware we build (containing, amongst others, an ARM and a FPGA), I added tcl scripting of the kernel driver interface for the FPGA for testing, debugging, fun & profit ;) ..although that has no visual side.

GUI builder for desktop applications in 90s were really useful in increasing the productivity of programmers. It is sad to see how complex it is to build the UI of a web application in comparison. And there is no definite answer on the best way to do it neither.

Of course now you can expose your app to the whole world. But instead of thinking what it means at the application level you spend lot of brain cycles just setting up the styles and uncoupling presentation and logic.

I wonder if we'll ever see a middle ground take over where apps are developed in that 90's GUI builder style but instead of purely desktop applications, they're more akin to tiny internet applications like this idea from Rebol: http://www.rebol.com/reblets.html

Did you try that? Was it good?

I've never tried it, no. Just something I've read about in the past and it seems like something that could be easily done with Tcl and its "safe" interpreter mechanism.

Indeed! I've been trying to figure out if we MUST sacrifice such productivity and K.I.S.S. to get web or web-like features for rank and file CRUD intranet apps. Are the bottlenecks solvable? Related debate:

https://www.reddit.com/r/dotnet/comments/kn20yi/start_with_a...

Until Node (when it was more than 10 years old), JS essentially did not exist outside the web.

And other languages essentially didn’t exist inside the web.

So JS’s success is the web’s success, other explanations are not helpful or needed.

I wouldn’t characterize JS as fun either, especially not in comparison to Python which predates it.

Funny how that came back into vogue. Netscape web server had a JS runtime way back then. Node is way nicer to use though.

I also remember around the same time it was possible to run TCL in browser, like Java applets.

You could run lots of things with the right plug-in/activex component. And even VBScript on IE/Win. But Netscape Navigator was not yet dead, so the only reliable browser scripting language was JS.

> Netscape web server had a JS runtime way back then.

And "applogics", in JS, IIRC. Touched it a bit in the 2000s.

> And other languages essentially didn’t exist inside the web.

Having trouble following your argument. What were people doing with PHP if not "inside the web"?

The argument is that since Javascript was the only programming language running in the browser, it was bound to be successful with the explosion of the web ; other arguments trying to justify why it succeed are not relevant.

> Tcl/Tk wasn’t fun

That is exactly the opposite of my experience with Tcl. It is one of the most fun languages I've used. And it's flexibility is without peer excluding other Lisp-y languages. So many fun things you can do.

Agree. Just the other year I discovered {*}, oh how that simplified some things.