I just don't see what people think others would understand by teleologic statements like: "write Go the way it wants to be written"
well, this is a very general advice, approx. implying : "don't force your previous language's world view while programming in Go".
f.e. if you are coming to Go from say Java, where everything is a class and where hierarchies abound, when you try to write a 'javaesque' go, you would be fighting against the language.
however, embracing a 'goesque' worldview of composition+interfaces as primary vehicle for program design, would/should make the overall experience quite a pleasant one.
To me it means "Read what the creators thought about when creating Go and how they view it, and do the same". But really that applies to any craft that exists: instead of trying to apply and adapt what you already know, clean your mind and start from scratch.
well, with knowledge i hope there is wisdom as well to apply it in a manner befitting the context.
Why?