This was a great read, but even more interesting was all the work on the author’s GitHub:<p><a href="https://github.com/digital-fabric" rel="nofollow">https://github.com/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://trio.discourse.group/t/structured-concurrency-in-ruby/314/10" rel="nofollow">https://trio.discourse.group/t/structured-concurrency-in-rub...</a>
Just for the note, in JS these two:<p><pre><code> async function foo() {...}
function* bar() {...} // 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's?<p><a href="https://php.watch/versions/8.1/fibers" rel="nofollow">https://php.watch/versions/8.1/fibers</a>