📝Get your *FREE Golang Cheat Sheet* - golangdojo.com/cheatsheet

I'm converting my project from Python to GoLang. It was great experience. Thanks for such a great video!

i've always presume that OOP is a must in any programming languages. Go is like a whole new world to me

So, I get into the discussions a lot. The problem with inheritance isn't inheritance itself, but the fact that is so often misused (and indeed misunderstood). Full disclosure, I am primarily an OOP developer, I just think in objects. I really like your point about duck typing, and I think if more people understood that idea, inheritance wouldn't get such a bad wrap. Example... take the super class A. It has a set of functions that are useful for other things. But it IS a thing. If you decide to inherit from A (class B extends A), the very first question you should ask is "is B an A?"... the problem is that a lot of people (anecdotally speaking for myself and 20+ years of experience) might look at the methods within A and say "yeah, that is what I want to do". This is NOT a good reason to inherit from that class. I have seen it so many times. And where you run into problems is when something DOES change with class A!, It will generally not (assuming the overall architecture is good in the first place) affect subclasses that ARE an A! What it WILL affect (and usually adversely) is a random class that just wanted to use the functions that already existed within A (but that are not As themselves). So, I do love the duck method you refer to. I think that should be the rule in OOP (not just with inheritance, but with interfaces and polymorphism in general as well). Thanks for the video. I am getting deeper into Go and find your content very useful.

In 6:26 you don't need to include the "super struct" as a variable just remove "human" from line 13 and the struct is "inherited"

As I learned it at uni, inheritance is not a necessary part of OOP, subtyping is. It is often conflated in many programming languages, but doesn't have to be. Inheritance is basically about code reuse, subtyping is about a more formal relationship between types, see the Liskov substitution principle.

8:10 it is a state of mind. GO does lack subtyping via class inheritance but composition over inheritance is a thing in Java, C# etc. and is actually prefered. Class inheritance is still useful when you want to hide some library/framework glue inside base class, but it can be achieved in other ways. I like GO, but languages like C#, Scala, Python, etc. happily mix OOP, procedural, functional and work just fine.

Encapsulation is not about making some data private , this is called data hiding. Encapsulation as defined in the object oriented through process book is about making data and behaviors ( methods ) into a single unit

Could you please make a video about Golang modules, thank you.

What you said at 8:05 simply cannot be overstated!

This is my favorite channel of golang content.

OOP: Birds fly Procedural: Birds are flown

Really enjoying the vids. Many thanks!

Nice video dude. really well produced and answered the questions I had

You mentioned in oop one danger with inheritance is changing a super class method causing breaking changes. How does go solve this issue? Based on composition the same problem exists?

Can u make video about Go packages? Best go packages or most useful

So I still don’t understand, if you don’t use OOP in Go what do you use? I’m still a noob so don’t know everything.

That is something I'm interested in 🤗

Yes surely need a deeper understanding of Interfaces please..!!

programming or hooogramming?

I'm learning Go for a college assignment and I've been liking most of it but the OOP-like stuff is so damn verbose and overly complex Also I don't understand the problem you mentioned with inheritance in OOP languages, seems like a non-issue, just don't put errors in the base class??

Thank you soo much for this!

Let’s get rusty guys

I stopped using GO for this reason. Its fine for little projects but designing anything substantial it quickly becomes a mess. I am actually in the process of converting everything to C++

👍

Is golang OOP?

I think that's a mistake by yours. You think OOP ist class oriented. But that's not true. Alan Kay's definition here: “1. Everything is an object, 2. Objects communicate by sending and receiving messages (in terms of objects), 3. Objects have their own memory (in terms of objects), 4. Every object is an instance of a class (which must be an object), 5. The class holds the shared behavior for its instances (in the form of objects in a program list), 6. To eval a program list, control is passed to the first object and the remainder is treated as its message”

OOP can't be but funcional its a joke hahahaa without having map, filter and reduce ^^

No Go is crap-oriented. I can't believe no other GC-based language have attempted to do what Go did before, which is compile to native code directly. There are efforts in this direction in .NET but honestly, it's late with modest results

Please Stop using this artificial vocie! I sure your video will be better with your natural voice. you triying to much with the voice.