There was a surprisingly large "enterprise" crowd using Tcl, as it's pretty great for self-contained environments. You have to generate the binding to your own

There was a surprisingly large "enterprise" crowd using Tcl, as it's pretty great for self-contained environments. You have to generate the binding to your own proprietary legacy interfaces anyway, and lots of situations benefit from proper event handling and easy enough GUIs (esp. canvas graphics). And every enterprise GUI looks bad anyway, so complaints about Tcls' L&F were rare. I think it missed some important opportunities, and was too focused on GUI stuff. And after all, the Perl/Python/Ruby bindings to Tk weren't that bad, either. In the early days of the web, tcl actually was a pretty good option (as a rival to Perl/CGI). And aolserver was pretty neat (still is, I'd say). But then it didn't go with the times, gtk/Qt stole the Unix OSS GUI thunder, RMS ranted against it, lua came along for embedded interpreters, Ousterhout moved around from Sun, to Scriptics to whoknowswhere… It's easy enough to miss your window. At least it's still more popular than Pike… I wouldn't rule out a small comeback, there aren't any technical reasons against it, it's well maintained, fast, has a very good codebase etc.