OOP and Go… Sorta
Amy Chen

I don’t have a background in OOP, so I don’t quite have the same appreciation for what Go leaves behind and what capabilities I might be missing if I don’t have, polymorphism, inheritance, etc. I suspect the answer is nothing, and that we just solve problems in different ways.

The Go Walkthrough series by Ben Johnson is really starting to give me a feel for the role of interfaces, but without the OO background to compare them to, I struggle to appreciate what is different.

One thing that I would love to hear more about is the ‘why’. Why did Go chose to do things differently?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.