It's what I ran into with threadbutler - I was in a while-loop and didn't want
to have an exception every time the thread looped.
Like, naive implementation of a thread server:
- Check if you have messages
- If you do, process them
- Check if you have async work
- If you do, do a bit of it, if you don't, then sleep for 1-2ms to avoid
hotspinning the CPU

With chronos that looks a lot more elaborate, avoiding the sleep and instead
powering the CPU down at the end of the loop during which it also does async
work, and only being able to wake up once another thread sends it a message
and pings it to become awake again