Explaining Ruby Fibers

This was a great read, but even more interesting was all the work on the author’s GitHub:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;digital-fabric" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;digital-fabric</a><p>Sharon is essentially developing a whole new stack of Ruby core libraries updated to feel more 2021 web than 2006 web (but in a good way). There’s a lot of neat stuff here to explore.

Does anyone know of if the issues brought up by njs in this thread still apply? <a href="https:&#x2F;&#x2F;trio.discourse.group&#x2F;t&#x2F;structured-concurrency-in-ruby&#x2F;314&#x2F;10" rel="nofollow">https:&#x2F;&#x2F;trio.discourse.group&#x2F;t&#x2F;structured-concurrency-in-rub...</a>

Have to admit, clicked on this expecting to learn about some sort of exotic optical fiber.

Just for the note, in JS these two:<p><pre><code> async function foo() {...} function* bar() {...} &#x2F;&#x2F; a.k.a. generator </code></pre> are fibers. These are execution contexts that JS VM can be switched into. The first one (asynchronous function) uses kind-of preemptive multitasking (implicit context switch) and generators are closer to canonical fibers - cooperative multitasking with explicit yield of VM to other fibers.

How do the fibers being introduced in PHP 8.1 compare with Ruby&#x27;s?<p><a href="https:&#x2F;&#x2F;php.watch&#x2F;versions&#x2F;8.1&#x2F;fibers" rel="nofollow">https:&#x2F;&#x2F;php.watch&#x2F;versions&#x2F;8.1&#x2F;fibers</a>