Hey Thomas, I see your point but personally I can't agree Go is object oriented. Inheritance is not that useful, we all learned that therefore is not included in Go design. I would say Go is behaviour driven and has interfaces/typed functions to allow abstraction/extendibility/all kind of useful patterns for maintainable software. That's it. People are forcing the Object Oriented nature on it for no good reason imo.
Not to forget to mention, in Go are functions first class citizens and Go has (of course) closures.
It is hard to clearly categorize Go.
But "kind of" is good enough for me as a category.
Fair enough. I mean, the official Go resource I quoted in the article also categorized it only as "kind of" so you are not far away from official Go maintainers! :)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.