Roman Samoilov | Rage

@codewithrage

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

United Kingdom

Pinned
Roman Samoilov | Rage
@codewithrage
Jan 20
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
1
Roman Samoilov | Rage
@codewithrage
Jul 31
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?
2
Roman Samoilov | Rage
@codewithrage
Jul 9
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
Jul 1
Who said API-only can’t be full-stack?
2
Roman Samoilov | Rage
@codewithrage
Jun 9
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 🧵
1