taiga

Newsletter

The page the header bell and the footer link point at. Everything on it is content — the theme brings the form, the frame around a sample letter and nothing else.

#Subscribe

Leave your address and a confirmation letter arrives. That is double opt-in: until you follow the link in it, you are not on the list — protection not from you, but from whoever might type someone else's address here.

A demo form: this site has no endpoint behind it, so a submission ends in the error state.

#What arrives

On a real site this is where the promise goes — in the site owner's words, not the theme's:

Queues: GRQ, LRQ and work stealing

taiga <news@example.com> to: you

//taiga16.09.2026

Hi!

In the previous part we gave the scheduler one shared queue of runnable goroutines and put a mutex on it. That works — right up until there are eight cores.

Part three is about the way out: every P gets a local queue and a slot for the goroutine that was just woken, an overflow spills half of itself into the global queue, and an idle P goes stealing rather than waiting to be fed.

Read the guide → example.com/run-queues/

— the author

P. S. Next part: what the scheduler does when a thread gets stuck in a system call.

You are getting this because you subscribed to the justskiv.github.io newsletter.

taiga. You can reply to this letter — I read every one.

#What never arrives

The short list is the actual promise: no "just checking in" letters, no other people's courses, no seven-letter funnels after signup.

Past issues On a real site, a link to the issues themselves.