Read on Twitter
Whenever someone from Java or C++ or C# comes to Go, they look for "class", find "struct", and stop looking. #golang
This misses two fundamental differences between Go and "traditional" OO languages. (But for "traditional" read "recent, mostly C-derived".)
The first is that it's not only structs: Any concrete type can have methods: ints, bools, slices, even funcs: golang.org/pkg/net/http/#…
But the more important idea is the separation of concept: data and behavior are two distinct concepts in Go, not conflated into a single notion of "class".
That is the insight (which goes all the way back to Smalltalk) on which the OO type system, including the interface model, is built.
Stopping at "struct == class" misses much of what makes Go work.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
