Linked by Thom Holwerda on Mon 11th Feb 2013 22:59 UTC
General Development "I feel like writing about the Go programming language (or 'Golang') today, so instead today's topic is computer stuff. For the record, the language I've programmed the most in has been Python, so that’s the perspective I'm analyzing it from." Some good and bad things about Go.
Permalink for comment 552397
To read all comments associated with this story, please click here.
RE[9]: My thoughts on Go
by satsujinka on Wed 13th Feb 2013 22:33 UTC in reply to "RE[8]: My thoughts on Go"
satsujinka
Member since:
2010-03-11

If you use interfaces as a primary means of tagging your objects then, yes you can't do that in Go.

However, interfaces aren't just a means of saying this object can do this, that, and the other. The methods of an object do that just fine; there's no need to be redundant. Instead, Go uses interfaces as a contract. If I need a Reader then I'm going to be using a Read method. Which object this is doesn't matter.

I commented on this earlier, but Go's interfaces are backwards in comparison to most others. It's not the object that implements an interface, but the interface that defines an object.

Reply Parent Score: 2