News for hackers. Stuff that matters.
Re:Visual Tcl by flohofwoe on Wednesday January 27, 2021 @07:35AM (#25927439)
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.

Re:Visual Tcl by Pet_Ant on Wednesday January 27, 2021 @09:38AM (#25928753)
> 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

Re:Visual Tcl by FlyMoreRockets on Wednesday January 27, 2021 @11:40AM (#25930318)
Not sure why you are being downvoted, you aren't wrong.

How does it compare to Python?

Re:Visual Tcl by 7thaccount on Wednesday January 27, 2021 @02:34PM (#25932801)
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.

Re:Visual Tcl by Pet_Ant on Wednesday January 27, 2021 @03:00PM (#25933152)
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"

Re:Visual Tcl by dlundqvist on Wednesday January 27, 2021 @09:38AM (#25928752)
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.

Re:Visual Tcl by ephaeton on Thursday January 28, 2021 @04:58AM (#25940077)
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.