Go is pretty awesome at managing memory and there is no better resource to understand it than its reference page; it is pretty dense ⚡ The document goes in-depth and covers literally everything you need to know about it, from its model, the intuition, the trade-offs, the sync primitives, locking vs message passing, and more importantly which sync primitive to use and when along with potential pitfalls. give it a read: go.dev/ref/mem If you write Go programs, this document is a must-read even if you just want to write good Go code and not dive deep into internals. ⚡ I keep writing and sharing my practical experience and learnings every day, so if you resonate then follow along. I keep it no fluff. youtube.com/c/ArpitBhayani #AsliEngineering #Go
Its a nice read with a great advice 😄 . ⚡ If you must read the rest of this document to understand the behavior of your program, you are being too clever. ⚡ Don't be clever.
bhaiya I want to start learning GO from scratch, what are the best resources you know and what is the best way to learn GO??
Have recently encountered "proficieny in Go" in few Data Engineer opportunities, if possible, can you share how it can replace Python in efficiency or performance
Last time I opened that page, it was suggested that I was being clever if I were about to read the whole thing and was also warned that I shouldn't be clever. 😄
Wasn't aware of it! Added to my important to read list 🔥
Liking post => sending to my ToDo list
Good post!
⚡ Admissions for my System Design August cohort are open, if you are SDE-2, SDE-3, and above and looking to build a rock-solid intuition to design any and every system, check out arpitbhayani.me/course