► Join my Discord community for free education 👉 https://discord.com/invite/Ac7CWREe58
► Exclusive Lessons, Mentorship, And Videos 👉 https://www.patreon.com/anthonygg_
► 50% OFF on my Golang course 👉 https://fulltimegodev.com

Thanks for watching <3

As soon as he said "YavaScript" I knew he was gonna cook 🔥

Short explanation: It's like C

10:31 "Golang is only about Structures, Data and Functions. That's the only thing you need to know." ❤

Good explanation. As a note to others still confused, structs are passed by value by default in Go (what Anthony means by copy; it's not the original, remember that) and thus when we create a pointer we have a reference to the memory, which will not be cleared with the function stack.

Dude… thank you so much for this, cause I literally asked you about this yesterday and today you have a video on it. God bless man!

For anyone looking to better understand Go, I'd recommend implementing OOP in pure C.  Structs are essentially wrappers that hold data so you can easily manipulate related information. Methods are just functions with an inferred argument, and access modifiers are just structs that forward method calls to internal structs.

Wish this video existed when I first started writing Go. Really well done and easy to understand for OOP programmers starting Go!

I come from a Python background. When I started learning Go, I found myself constantly comparing its features with Python, which made my understanding a bit difficult. However, this video completely changed my perspective on how I should approach learning Golang.🙇

This was the first in a series of big breakthroughs for me using GO. Thank  you, Anthony!

One thing that I like about hanging functions off of structs is that code bases are far more discoverable via lsp

if I'm not wrong, I visualized the struct as a columns in a table with different data types and you use functions to insert data .

The structs in Go, C, Rust are just the data. In memory there only exists the data.

In python and JavaScript each piece of object comes with the data just as the previous language, BUT it also has a bunch of other data that is not what u declared, for example a pointer to its class and the methods. For python for example it even holds onto the methods.

1st type of Language:

[an object]
- field 1
- field 2

And then somewhere else you have:
- function 1 that takes in the type of struct as an argument

Whereas the 2nd types of languages:

[an object]
- field 1
- field 2
- method 1
- method 2
- class metadata
…..

This roughly can be what u can imagine the general differences

I struggled to understand pointers and your explanation was mind opening. Kudos.

this thinking is what felt closer to originally and got confused with with languages that abstracted away this mindset ❤

I see golang as having Objects, but not a strictly oop language. They are objects though. There is encapsulation, interface boundaries, references, GC'd memory. And there is kind of a way to inherit from other structs, but it is more like your adding another struct to yours, not "real" inheritence.Maybe those aren't "methods" in the strictest sense, but thats basically just semantics of defining "Self" in other language method syntax, so like tomato tomautoh

Thanks for the video. Took me a couple mins to realize its "classes", not "clauses" :)

Your examples made my confusions alot clear, ty alot <3

I saw a comment saying interfaces, i think you should show when to use interfaces and methods. Good video.

I really like the way you explain things man, great work!