Fulfilling a Pikedream: the ups of downs of porting 50k lines of C++ to Go. | To:goto To;
https://togototo.wordpress.com/...ling-a-pikedream-the-ups-of-downs-of-porting-50k-lines-of-c-to-go/
"""
The tl;dr
In business terms, the project was a success: completed ahead of schedule, performing acceptably, and less than 10k LOC long (this massive LOC reduction was of course partially due to the removal of features that were deprecated or not needed by the team behind the rewrite). In personal terms however I feel the outcome was suboptimal, in the sense that I wrote two to three times as much code as would have been needed in a language with parametric polymorphism. Some of this was due to type-safety: Go forces a tradeoff to be made between verbosity and type-safety, and I settled somewhere in the middle; it could have used less code and been less type-safe, or used more code and been more type-safe.
"""