Roman Samoilov | Rage

Fiber-based framework for teams that love Ruby but need fewer reasons to explain why they’re still using it.

[Roman Samoilov | Rage @codewithrage]

Why is Ruby losing ground? It's not because the language is "dead" - it's because our tools haven't evolved to meet modern performance and stability needs.

I built Rage to give Ruby teams the missing pieces they've been looking for in other ecosystems.

A thread on the mission behind Rage:

[Roman Samoilov | Rage @codewithrage]

@jpcamara @TheDumbTechGuy @inazarova @tenderlove Amazing! Are you using Rage skills?

[Roman Samoilov | Rage @codewithrage]

@SaviourOfSoil @jpcamara @TheDumbTechGuy @inazarova @tenderlove I don’t really see it being slower, except on the Room page.

[Roman Samoilov | Rage @codewithrage]

Full results: https://t.co/blvkixXMwk

[Roman Samoilov | Rage @codewithrage]

Just reproduced the official Basecamp’s Pi benchmark with Rage.

Rage replaced Rails+Puma+Resque+Redis, handled 10x clients, with ~22x the deliveries per second and ~4x less memory per connection.

[Roman Samoilov | Rage @codewithrage]

Source code: https://t.co/xrxECgn1nG

[Roman Samoilov | Rage @codewithrage]

The most common piece of feedback I got about Rage? “API-only sucks.”

So I shipped the official Inertia.js adapter. Auto-starts Vite in dev, pre-builds assets for prod, exposes Inertia props out of the box.

What’s your next excuse?

[Roman Samoilov | Rage @codewithrage]

Source code: https://t.co/xrxECgn1nG

[Roman Samoilov | Rage @codewithrage]

Rage just got daemons.

Rage::Daemon lets you run long-lived background processes alongside your app.

No external process managers needed. The processes your app depends on now have a home inside the app, supervised by the framework.

[Roman Samoilov | Rage @codewithrage]

@seuros Just following a pattern really - Inertia adapters all start with “inertia-“.

https://t.co/00trSJYVB7

[Roman Samoilov | Rage @codewithrage]

Who said API-only can’t be full-stack?

[Roman Samoilov | Rage @codewithrage]

Benchmarks across a full request cycle - request in, connection pool, database query - show the 2.2x to 4x improvement. In 30 lines of code.

Simplicity-driven development wins again.

[Roman Samoilov | Rage @codewithrage]

For several months, I wanted to optimise the code in Rage that schedules fibers to be woken up at a specific time. The plan was to use skip lists.

Last week, @maciejmensfeld’s compilation of Ruby performance PRs got me inspired, and I decided to give it another look 🧵

[Roman Samoilov | Rage @codewithrage]

Looking back at the previous example, if 1000 fibers try to fetch a connection from an empty pool, each new timer will be `Time. now + 5` - i.e. higher than the previous one.

Which means that if we first check the last element in the list before doing the O(N) insertion, we can get constant-time insertions in the most common scenario.

[Roman Samoilov | Rage @codewithrage]

Recurring background tasks in Rage are one config block away.

Background tasks run on fibers - light, fast, and in-process.

[Roman Samoilov | Rage @codewithrage]

The common Ruby advice - “default to threads, only reach for fibers if you’re I/O-heavy” - is backwards.

The worst case for a fiber-based server is thread level performance.

The downside isn’t really there. The upside is.