One suggestion I have is to just stick with one language instead of using multiple languages in the series. I understand that you are using different languages to prove the point that ML can be implemented in any language, but when you switch the language between articles, it might get a little awkward to follow. I would suggest teaching in one language which you think can better represent the logic and then provide a link to a github repo or something which has the same code in different languages.
Again, kudos for the effort.
Since Go is a systems language, I have it running as a http server that sends back the results to webpage that renders the JSON on a HTML5 Canvas.
What I really wanted to do is experiment with "migrating" solutions from one population to another, to see if I can get any speedup that way. Right now, the isolated populations sort of converge at the same speed, but some do better than others, because they converge to different local minima.
Anyway, if you want to fork it, its here: https://github.com/YesSql/GolangTspGa
It'd only be a toy though. Because of the high number of evaluations used by these kinds of methods, and the cost of a single evaluation, most serious work is done in engines based on faster languages, notably Java, C, or, or C++.