How Go works under the hood 👀 ?

[yaten2302]

Hi @astavonin,

Your Go optimization guide is an great resource for understanding how to write efficient Go applications.

I was hoping to seek your guidance on understanding some of Go's internal design decisions (like go-routines, concurrency etc...). While I’m familiar with Go and actively contribute to CNCF open-source projects, I’m still trying to grasp how Go differs from traditional OOP languages — particularly how it handles concepts like inheritance and abstraction under the hood, given its minimalistic approach to OOP.

Would really appreciate any insights or resources you could share!
BTW, here's the link to my GitHub profile, I've all my PRs here - https://github.com/yaten2302 :)

Thanks!

[astavonin]

Thank you for the feedback. Honestly, I didn't plan to include all these, as I do not feel confident about how to describe that. I'll have a look, anyway. Let's try!

[yaten2302]

Sure, @astavonin ,
Since, I have been contributing to cncf projects for quite some time now, so that's why I was curious to learn more about golang internals. I found this repo, that's why asked 👍
If you have any other resources which may not be suitable to be listed in this repo, could you kindly share it here?
We can also connect on linkedin or on any other platform regarding the same (if required).
Here's my profile BTW - https://www.linkedin.com/in/yaten2302/ :)
Thanks