🔥The 9th Round of Easy Loan, Earn $40 Reward is in progress❗️ ⏰ Promotion Period: January 15th - Feburary 15th, 2025 👉 Register now and check more details at gate.io/campaigns/358

Just writing about sync.Mutex, I hadn't thought it was that interesting and even making diagrams got me more excited :s .... coming soon

"How sync.Mutex works" is out, as usual - a longgg story to know how internal stuff works. victoriametrics.com/blog/go-sync-m…

How about a post about maps in Go?

Not every open source company needs VC money to take off 🚀 In our latest episode, our co-hosts Robby & Timothy Chen talk with VictoriaMetrics Co-Founders Aliaksandr Valialkin & Roman Khavronenko about how they scaled their time series database and monitoring project and company 💫

The long story about maps is published, check it out: victoriametrics.com/blog/go-map/ A simplified version, but it still took me a whole week to write and make the visuals look catchy

Been drawing way too much today, I'm not even sure what I'm drawing, anyone else got a clue?

Cool, my post is featured in Golang Weekly golangweekly.com/issues/519

Sync.Pool's got just 2 methods: Get(), and Put(). But trust me, you'll need a bunch of diagrams like this to really get how sync.Pool works.

The mechanics of sync.Pool are here: victoriametrics.com/blog/go-sync-p… It's quite lengthy, so I’ve summarized some key points I discussed in this post: - Why should we return a pointer in New() of sync.Pool? - How is sync.Pool related to the scheduler or PMG models? - What is false

I've seen a lot of traffic from golangweekly lately. Looks like our post got featured again: golangweekly.com/issues/520

Go slices are pretty simple, but let's overcomplicate things with this long post :) victoriametrics.com/blog/go-slice/

(RTs appreciated) Today the waitlist opens for the latest byteSizeGo course, Building Production-Ready Services with gRPC and Go bytesizego.com/grpc-with-go This has been by far the most requested topic, and the depth Chris Shepherd has gone to means you really will leave the course

sync.WaitGroup is our target this week: victoriametrics.com/blog/go-sync-w… The interesting thing isn't how it works, but how its struct has changed through many versions.

I always forget the pattern of sync.Cond, it's time to model and bookmark it.

Go sync.Cond: victoriametrics.com/blog/go-sync-c…

If you're confused about when to use a pointer or value receiver, or whether to return a pointer or value, here’s what I’d suggest by default: - Return a value from a function instead of a pointer. You’ll likely reduce heap allocation and not get confused with shared data. -