Beginners Should Think Differently When Writing Golang 

Thanks for content! Anthony, which color scheme you use for code?

Thanks. 100% correct

When he said that I immediately thought if Go does that by default. Thanks for clearing that up.

Go passes everything by value, not just structs

@@yegorzakharov8514 so does C#, but some of its types are essentially pointers by default, so that’s what you’re copying as a parameter.

@@yegorzakharov8514yeah but sometimes the “data” being passed contains a pointer

Thank you!

Where 'this' is the default argument.

same words, accepted the Go way long ago, but the "syntax sugar" example made things connect in my head better

How does he move the cursor quickly up and down while typing ?

it looks like he is using vim movement.@@avonflex5031

@@avonflex5031 vim

@@avonflex5031, it is called VIM motions.

Thanks for the detailed amend

Cool explanation. Coming (and still mostly coding in) JS and Python, I'm loving Go's approach

Anything is procedural underlying. Whole OOP is fake somehow, there are data and data and data and data. Rules of privilege modifications and metaclasses are kinda mix of syntactic sugar and compiler/interpreter rules, which don't allow to compile run something which is completely possible if written in asm or something. Can't access private member? Nothing existing in C. C program usually can get in all memory program get from OS, there is nothing banned. OOP is cannot be done or implemented in asm, it's completely in scope of interpreter/compiler, but everything ends as asm code (or VM bytecode of you want) - but everything at the end, before executing, is machine code or one step before machine code - and there is no way how to do OOP in machine code, it can be only do by higher level filter which dones't allow somethinf what not fit OOP paradigm but in fact it is still doable by machine code and computer itself. So behind everything, from OOP to functional approach, is just a C-like or asm approach - memory and functions. Nothing more.

But if struct has methods attached to it, then every object of that type will have some data about its methods silently embedded by compiler? So it's not like in Go "objects" have only fields while in JS they've also got methods and class metadata... Or am I missing something?

@@adexitum im not sure I understand the question, the structs in Go, Rust, C are only the fields. Since the compiler always knows the type it does not need to embed the methods in the struct itself. if you use interfaces the struct WILL contain extra vtable data to be able to know which method to call. in JS its prototype-based so each object points to the class it belongs to and from there u can figure out which methods it has. but you can also dynamically add and remove methods, especially in python. so the objects are usually alot more bloated due to the dynamic and flexible nature of them

I don't have a py background, but also compared it to py :D

yeah dont take the advise of this youtuber, seems dumb advice tbh

Happy I could help out. You will do great coming from those languages.

Good luck my man

Default VIM plugin that comes with VSCODE

@@anthonygg_thx a lot! Very useful content❤

Gruvbox the hard contrast one

Now, that is a better explanation. Little nitpicking though, it's Typescript's feature. The interfaces are removed when transpilling TS → JS, as JS has no code structure like that.

U should use the Go method receivers. But I wanted to show that changing the syntax could give newcomers a better understanding whats going on

Like Anthony mentioned in a previous video, receivers are simply syntactical sugar for passing the struct to the function as a parameter. Whether that be a pointer or not. But, the go idiomatic way is definitely receivers. Lends to better readability.

gotcha, thank you

Minor issue: Go uses "nil" instead of more sane "null" (if only I could get a nickel for every time I type null instead of nil. )

🤩

Gruvbox

I haven't touched Golang yet... but It seems the man of the video is being dogmatic. He talks about syntactic sugar as it should be prohibited... all high level language ARE SYNTACTIC SUGAR. And when talking about testing... how would you mock for unit testing... or you don't unit test... This man is crazy... Tomorrow I will take Golang to start learning, but I have seen other opinions opposed to the one presented here... For this man Clean Architecture would be shit

@@maximilianosorich554 Not to be rude, but I think you didn't understand the video if you think he's making a point about (let alone against) syntactic sugar. He's merely explaining the difference between passing by reference vs. passing by value, which is something you don't usually have to think about in the higher level oop languages he mentioned.

Why would I be mad? 😊. No pointers do not replace classes. Pointers allow you to update memory directly.

> think more in terms of the memory Not necessary. Go is garbage collected, and so you can code like you do in JavaScript or Python until you are ready for pointers. I am starting out with Go and I apply the same rules as JavaScript: Simply copy values of primitives / literals (int, float, bool, byte...) and for something bigger I use pointers & references (structures, slices, maps...) I really like the explanation of pointers here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-sTFJtxJXkaY.html

Pointers are always NOT safe for concurrent usage. Thats where channels come into play.

Thank you @@anthonygg_ . I'm kind of new to Go and I still don't know all of its capabilities. Will read what "channels" are.Thanks!

even if it doesnt have methods it can still satisfy an interface, if said interface doesnt have methods

Gruvbox

This is the same in Go, except that "structs" belong to the "value types", if you want to call them that. slices, maps, channels, pointers and functions would then be what is commonly called a "reference type" so you dont really have to worry about pointers with those.

Nothing is passed by value in Python, the whole data model is referencial. If you need a copy, you have to directly use copy() or deepcopy() functions.

To add more to this, most oop languages a class could have a “hidden” vtable pointer for any methods that are overridden by the derived class. Since go doesnt allow inheritance this doesnt exist. Simply put: Go struct is a “class” without inheritance and which allow you to specify read only methods.

I love this C approach. Doing everything manually. You can fully make OOP in C, with only one reason - when you try something like access private member from outside, compiler/interpreter of OOP language doesn't allow it. C allows it. So private loses its sense. But all things like constructor, inheritance, polymorphism and stuff, it can be all simulated in C - and even OOP languages compile into byte/machine code with machine/procedural approach, with a boilerplate and bloat of helping tables and tables and tables and tables... and whole stuff made just to make classes working. But it's just only a layer of abstraction, nothing more.

True. But I have several videos covering this aswel. This video was a specific exercise taking a step back

Gruvbox

@@anthonygg_ thank you

No difference.

A struct is not an interface in golang structs are a way to structure your variable with custom data types. Golang has its own way of implementing interfaces.

@@sanjeevdandin9350 Thanks for the explanation.

Yes. They behave the same.

Thank you

SaveBook is just a random name I came up with to be honest. You need to understand that explaining things to new people is an art on itself, they need to make connections inside their mind. Using these names and other simple explanations really helps them to get a better grasp of the matter. Once they get better they will do their own due diligence to see that certain terms have a more deeper underlying meaning.

Uh, I understand! I like your vids - I'm amending, not criticizing. I don't feel empowered to criticize creations. But I feel like adding my 5 cents if I have something to add (-;

@@yarcat I agree with you dont get me wrong. There a lot of things wrong with saveBook 😅.

😇

I was trying to figure this out as well 😂