> Reading Go means that I keep having to read idioms (as posted in the article) and parse them back into the actual intent, What? I never have to do this... >

> Reading Go means that I keep having to read idioms (as posted in the article) and parse them back into the actual intent, What? I never have to do this... > I can't easily navigate to the definition of a function . . . I usually don't have tooling that can jump to definition What? You command-click on it... ? > jump-to-definition becomes impossible as soon as interfaces are involved, because structural typing makes it impossible to know what is an intentional implementation of that interface What? You obviously can't jump-to-definition of an interface, but in what way is this a limitation?