'it's still the defacto standard in the electronic design automation industry.'
Can you elaborate on that? I know nothing about that industry but I still have some nostalgia for Tcl despite of using Ruby now.
In the past I was a solid Tcl user (couple years ago even did a small custom Linux distro where bash was replaced with Tcl & installater was written in Tcl/Tk. It was fun!)
My thoughts on its ~ 0 popularity are:
* No Rails equivalent.
* No gems equivalent. In modern world it is a disaster. (One could notice how quickly nodejs got its npm.)
* 8.6 and OO system are in aplha/beta stage for 6 (?) years. Many of us just gave up waiting.
I still remember '2007 would be a great year for Tcl.' What a joke.
Tcl is used quite heavily as a command line shell EDA tools. Google "pt_shell tcl" or "ncsim tcl" for examples.
Cadence and Mentor Graphic's digital simulation GUIs were built with Tk. Probably a lot more. The big win for Tk in GUIs in the late 90's was it's cross platform support. For all of its limitations - Tk was a huge improvement over Motif!
Tcl is also used as a data file format for describing desing rules. Synopsys' SDC (standard design constraints) and Cadence's CPF (common power format) are both just design specific variations of Tcl. Writing a parser for these formats just requires writing command implementations. Tcl takes care of the rest.
Can you elaborate on that? I know nothing about that industry but I still have some nostalgia for Tcl despite of using Ruby now.
In the past I was a solid Tcl user (couple years ago even did a small custom Linux distro where bash was replaced with Tcl & installater was written in Tcl/Tk. It was fun!)
My thoughts on its ~ 0 popularity are:
* No Rails equivalent.
* No gems equivalent. In modern world it is a disaster. (One could notice how quickly nodejs got its npm.)
* 8.6 and OO system are in aplha/beta stage for 6 (?) years. Many of us just gave up waiting.
I still remember '2007 would be a great year for Tcl.' What a joke.