Ruby 3.0 and the new FiberScheduler interface
> all relevant standard library methods have been patched to yield to the scheduler whenever they encounter a situation where they will block the current fiber<p>This is huge.  They solved the function-coloring problem by deciding that all functions are now potentially async.  It makes it more likely that the ecosystem as a whole actually becomes async-compatible.  I wish Python had taken this approach, though I understand why they didn't.