‹ BackHN Continuity

Thread

Tcl/Tk 9.1

304 points · 144 comments · dmux

  1. srean · · focus · HN ↗
    I have a soft corner for TCL, because of its idiosyncracies and weird dynamic stringy playfulness. I would be wary of using it professionally but to play around for the fun of it ... it's just too much fun. Upvar and uplevels are crazy.

    Python is that kind of cool one behaves when visiting parents of your would be spouse for the first time. Tcl on the other hand is like playing one's secret exclusive and somewhat dangerous games with kid school bestie.

    Tcl/Tk pioneered the notion of a scripting language as a library. It got threading right. You can run multiple independent Tcl interpreters in the address space of your process and they can exchange messages. Entirety of interpreter state is encapsulated inside the interpreter object, no globals. To a user an it is just a pointer to an object.

    No need for GIL, no need for serialization/deserialization (pickle/unpickle) ... just within process memory copy (or no copies in case data is immutable).

    1. zitterbewegung · · focus · HN ↗
      Sort of interesting how Python has got rid of the GIL. Serialization of data securities is still something relevant though and I’m not sure if you should use pickle still?
      1. tlavoie · · focus · HN ↗
        Pickle is likely still handy, as long as you created the data that you're deserializing. Zope's object database was a big pickle file, as I recall. But yeah, not a good idea if you're cracking open user-supplied files in any way.
        1. vkazanov · · focus · HN ↗
          Ha! People still remember Zope!

          That was my first web kind of framework. The naivette of Zope still amuses me endlessly to this very day.

          It tried to be cool, made ALL the wrong choices, and died silently with people just moving on.

          1. pjmlp · · focus · HN ↗
            There are dozens of us. :)
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.