7 ms·
So, I end up using TCL at work, and I hate it. I'm trying not to let the hate bleed out here, but why in the world is anyone still using this language? If it's
by hardwaresofton 13y ago
So, I end up using TCL at work, and I hate it.
I'm trying not to let the hate bleed out here, but why in the world is anyone still using this language? If it's for TK integration, there are other options
- anon35 13y agoA lot of well-reasoned arguments are laid out in the Tcl advocacy page here: http://wiki.tcl.tk/590 http://wiki.tcl.tk/590
- hardwaresofton 13y agoThanks for link, will forward next time someone complains around the water cooler
- davidw 13y agoAntirez' comments on Tcl are also worth reading: http://antirez.com/articoli/tclmisunderstood.html http://antirez.com/articoli/tclmisunderstood.html I think you appreciate Tcl the more you see how it's built under the hood. I'm guessing you're using some crufty EDA stuff though, where you're not seeing the good side of the language, and dealing with a lot of accumulated baggage.
- tptacek 13y agoIt is an extremely simple language. It admits to enough metaprogramming to do many useful DSLs; it's always been a half-ass version of Lisp in that regard, but with more congenial syntax, and before any other language embraced the idea. It was the first of the scripting languages to do a truly good job at embeddability. incr Tcl has a very clean design. The language is designed from the bottom up to work well in event loop programming, in much the same way Golang is designed for lightweight threads. It's true that the language hasn't aged well, and I have a hard time coming up with an example of a project I'd bring it into (for extreme embeddability I assume I'd go with Lua; for DSLs I'd use a Lisp dialect or Ruby [aka Japanese Tcl], and object oriented design has fallen somewhat out of fashion. Do you work at Cisco?
- hardwaresofton 13y agoThanks for the breakdown, I agree with these things, and it does blur data and function, which I have seen in some code segments. And I'm not without thought on the subject, I mean I know it pairs super well with C and there's a reason I deal with so much legacy code in it. It just sorta blew my mind that people still want it around enough to have conferences about it. The first time I left an unbalanced close brace in a comment, I started to dislike TCL (I mean, it's not the worst thing in the world), maybe I was hasty, but if other languages can solve that problem, it seemed hard to fathom why TCL hadn't solved or at least patched to fix it yet (maybe also the version we're using is outdated) And no, not Cisco, but a more-hardware-than-software company
- tptacek 13y agoDon't get me wrong, I can go all day on what I don't like about Tcl. In 1997, the startup I was at had me design and implement a programming language (long story); in '99, the cofounders at my next startup convinced us to use Tcl, and I still vividly remember that the language parsed freaking comments; you could get a syntax error in your comments. It's not a great language. It was, though, at the time, a pretty good tool for building some kinds of programs. Tk is pretty gross; I'm always weirded out when people say that's the reason they like Tcl.