Johnny Sins is truly a modern polymath!
After 7+ years of senior python thinking for me this was the 'AHA' moment right here: " team := make([]Player, 11) for i := 0; i < (len(team) - 2); i++ " I was like 'what???, you can loop over a slice of "capabilites", not just actual objects???" I think this opens a whole range of different design ideas, way of decouplig, testing, etc. Cos you're focusing on the capability, not the object / instance or whatever. Now the term 'contract' makes a lot more sense. Because you are saying, hey I don't care WHAT you are as long as you CAN DO this or that. BTW, thanks a lot Anthony! In addition to the depth of your (applicable real life) knowldge I really like your style. Feels likehaving a coding conversation in pub w. a beer. :)
probably the video I was looking for.. Thanks Anthony!! Gonna learn so much from your channel.
btw the vscode theme is Gruvbox
This clears things up for interfaces with GO. Keep up the good work !
The KickBall function of Player structure was kinda misunderstood....
Thanks for this! You gave me that big AHA and thumbs up for using VIM 🎉
the best way to learn go is this chanle
thanks dear finally i understand interfaces...
Hi Anthony, how do you use rand without seeding?
😂😂Got to learn with comedy characters! CR7 and Suuuii Fked Little less messi 🤣 15:41
People on Java / Any proper/general OOP: wtf this sh*t. make life so hard The same people on broken Go's Interfaces: this is awesome. make life so easy. If you don't want OOP, it's fine. But don't force it half-baked. having interface without class are so stupid.
Hi Anthony, I'd like to ask you, why did you move to vscode from nvim? Just curious.
i found a big mistake in your video, Messi>ronaldo.
Am I missing something? Imo this videos just explains interfaces as in any other language, the main benefit/difference of interfaces in go, which is them being implicitly implemented and not defined before you need them kind of gets lost.
@anthonygg_