See my reply here for the problems with that: https://news.ycombinator.com/item?id=36926392 https://news.ycombinator.com/item?id=36926392 EDIT: To elaborate m

See my reply here for the problems with that: https://news.ycombinator.com/item?id=36926392 https://news.ycombinator.com/item?id=36926392 EDIT: To elaborate my reply there tailored to your lawn mower example... > What mows a lawn? A person, or machinery? Yes, in this case the tool analogy matches real life (and your interpretation of Go interfaces as tools): I use a lawn mower to mow the lawn. My issue is that there isn't always a tool, but the Go worldview forces there to be one: What reads a book? A person, or a ...?