>only true if the duplication: a) isn't also an abstraction (which, in go, it is in this case) Can you give an example? I don't follow. I generally don't like

>only true if the duplication: a) isn't also an abstraction (which, in go, it is in this case) Can you give an example? I don't follow. I generally don't like abstractions for the sake of abstractions. I use Go's interfaces for a very specific reason: when I want dynamic dispatch, but with nice static typing guarantees. Interfaces in languages without structural typing force you to design a rigid, unflexible hierarchy/ontology well in advance, which only gets in your way when requirements change. >is "contained" (i.e. not overly used) Can you show why "containment" is necessary and why "overuse" is a bad thing?