We recently did a major migration from Next.js to Ruby on Rails with Inertia that took a few months. I wanted to share some of the thought process behind that decision, how we made it and what the change looked like in practice.
Inertia.js turned out to be amazing for this switch, and turned me into a big fan of Vite and Rails.
freddydumont · 14h ago
Did you miss the DX of React Server Components at all when switching to Inertia?
dyogenez · 14h ago
I haven't so far. I’ve preferred the new way:
With RSCs, I’d have code scattered throughout components that would hit APIs to get data.
With Rails + Inertia, that code is all in a Rails controller - usually with a serializer.
I’m still getting used to using InertiaRails.optional there which is what’s needed for a Suspense like experience w/Inertia. Having everything in controllers again is nice.
Inertia.js turned out to be amazing for this switch, and turned me into a big fan of Vite and Rails.
With RSCs, I’d have code scattered throughout components that would hit APIs to get data.
With Rails + Inertia, that code is all in a Rails controller - usually with a serializer.
I’m still getting used to using InertiaRails.optional there which is what’s needed for a Suspense like experience w/Inertia. Having everything in controllers again is nice.