Go's power is in emergent behavior
I'm not sure I understand why implicit interfaces are better than explicitly declared interfaces. (This is an honest question.) I do iOS stuff occasionally, and in that world one of the main purposes of interfaces (in Objective-C, protocols) is to explicitly declare that some entity adheres to a contract - it promises to implement some pre-agreed-upon functionality that other entities can use. What do implicit interfaces buy you? Better static type checking? Less typing?<p>/* Also, from the blog:<p>> Nowhere in this code did we ever declare a relationship between MyType and Answer.<p>"Answer" isn't in the example. Was this something from an earlier draft? */