Hey folks, the author of the gem is here. Thank you for all your feedback. I value it a lot! First off, I have changed the API-only bullet point. I wanted it to be short and clear. I didn't mean to sound arrogant. Sorry…
I totally see how you might find these benchmarks irrelevant or "unfair". But there are no lies - I didn't make those numbers up. These are pretty standard benchmarks showing the overhead of a framework and how it…
> Should the calling code wrap the database calls with `Fiber.await { Fiber.schedule { ... } }`? Nope. Scheduling works seamlessly, thanks to Ruby core.
Hey folks, the author of the gem is here. Thank you for all your feedback. I value it a lot! First off, I have changed the API-only bullet point. I wanted it to be short and clear. I didn't mean to sound arrogant. Sorry…
I totally see how you might find these benchmarks irrelevant or "unfair". But there are no lies - I didn't make those numbers up. These are pretty standard benchmarks showing the overhead of a framework and how it…
> Should the calling code wrap the database calls with `Fiber.await { Fiber.schedule { ... } }`? Nope. Scheduling works seamlessly, thanks to Ruby core.