As a long-time Tcl/Tk user it seems where some might think Tcl went "wrong" was combining its Lisp-like semantics with C-style syntax. The "hybrid" was confusi

As a long-time Tcl/Tk user it seems where some might think Tcl went "wrong" was combining its Lisp-like semantics with C-style syntax. The "hybrid" was confusing to many programmers, especially those coming from C and similar tools. The article mainly examines the corporate and marketing aspects of Tcl's history, and not so much the technical merits of the language. True enough, Tcl lost out to Java and other languages on that account but as the article acknowledges Tcl still has quite a large community keeping it going. On the technical side, the commentary about "everything is a string" has been extensive discussed and IMO has been shown to be more than not a red herring. In any case many of the "warts" that were prominent in 2010 have been at least partially addressed. Notably in recent years Tcl as acquired many Scheme-like features, an official OOP facility, and coroutines among other "modern" features. Tcl remains incredibly flexible and adaptable to diverse problem domains. I wouldn't try to write a hardware driver in Tcl, but for many problems it's the most productive tool in the toolbox.