8 ms·
The fiber scheduler solves this as concurrent execution is now built into the core of Ruby 3.
by ioquatix 5y ago
The fiber scheduler solves this as concurrent execution is now built into the core of Ruby 3.
- joelbluminator 5y agoDo you think it's perhaps confusing to call it async ruby? I was sure it works similar to node's async event loop but actually the fiber / fiber scheduler thing is more related to threads and doesn't use an event loop (?). It doesn't really matter I guess but the terminology "async" is kinda used in javascript land to mean event loop and afaik that's not what you're working on here right?