Imagine a language in which was so easy to write code that code flowed from a thousand keyboards, simply and correctly.
Imagine a language where it is so easy to roll your own OO system that you forget that code reuse was one of the key reasons you did it.
Is that what we've got ourselves in Tcl?
If so, Tcl is a victim of its own success.
This page is for qualities of Tcl which properly fall simultaneously into both Things holding Tcl back and Things pushing Tcl forward, because the interplay between those two categories is what will steer Tcl toward what it will become, or will cause it to stick in place. Sometimes one relies too heavily on that which one does best, to the detriment of other things.