In short, I think Glenn embraced the differences and challenges of adapting TeX in Clojure from an educational perspective. I don't think he intended to port it quickly or verbatim.
Glenn wanted to head-to-head comparison to promote education. To explain, in Glenn's talk around 11:36 (https://www.youtube.com/watch?v=824yVKUPFjU) he says:
> While I'm glad that the source code of TeX is still available to study, I sure wouldn't point a new programmer toward it because we should not be doing programs today like we did then.
> But what might be really valuable is to have a modern reimplementation written in a modern functional style to study alongside [the original TeX] to see how much has changed and to appreciate what he have and the value of improved tools and techniques and the tradeoffs that have been made.
His slide on his educational goals can be seen at 12:06:
> Illustrate what's changed
> Demonstrate values of expressive code
> Provide real examples of expressing procedural algorithms in functional style
> Show how functional programs are easier to reason about
> Show different styles of optimization
It seems unlikely that doing two ports (first to Go, second to Clojure) would result in less work overall. I would not expect that a procedural-to-functional adaptation would be made dramatically easier by porting to Go first.
TeX may have fewer dependencies (given that it predates many libraries), so `Go` would probably a good target for an intermediate port - imperative/procedural, globals, goto support, static compilation.
Modernize this program in Go, then port it to Clojure.