Writing Better Go: Code or Data?
A Journey... I've been on a bit of an odyssey trying out various languages in case there is something out there that might suit me better than Go . After considering many others - and actually trying out C# , F# , and Kotlin - my feeling is that I will not be abandoning Go in the short-to-medium term (although I may well delve deeper into Kotlin). However, as with many journeys, much of the benefit comes from the travelling itself rather than achieving a destination. For the purposes of this exercise I ported a little utility of mine which unpacks a legacy file storage format to each of the aforementioned languages and tried hard to write idiomatically in each one. Doing this inevitably leads one to question the structure of the original code and also any ingrained habits that might have passed their use-by date. ...and An Outcome If I am sticking with Go, I really ought to think about trying to write 'better' Go. A Case in Point One of my pet peeves about