Re:How we rebuilt Next.js with AI in one week
by JustSkyfall on Tuesday February 24, 2026 @06:34PM
(#47145090)
Rails 8 is surprisingly good nowadays. It absolutely still has its share of problems (e.g. Bundler being slow, the frontend story being crappy without Inertia, lack of types which is a biggie, memory) but it is still a fantastic framework imo.
[ Parent
| on HN ]
Re:How we rebuilt Next.js with AI in one week
by dmix on Tuesday February 24, 2026 @07:06PM
(#47145415)
Why Inertia.js? I quite enjoy not using JS heavy frontends in Rails by leaning on Turbo and light Stimulus JS controllers where needed. My experience going hard into Vue+Rails was full of pain and I've rediscovered why server first makes everything easier to reason about instead of duplicating tons of logic + dealing with constant async issues (particularly around automated testing and complex data loading).
Re:How we rebuilt Next.js with AI in one week
by moviedo on Tuesday February 24, 2026 @08:14PM
(#47146002)
Inertia because it’s a plug-in replacement for ruby html templating aka erb. Try it out, it’s basically the same stuff you get from erb, without the need for Turbo’s web sockets. You get server side rendering, all the great BE stuff like server side validation, but no SPA headache.
I find the best DX with Adonis/nodejs and typescript.
Re:How we rebuilt Next.js with AI in one week
by igravious on Tuesday February 24, 2026 @08:22PM
(#47146078)
Somebody should port uv to Ruby :/
Re:How we rebuilt Next.js with AI in one week
by cheshire_cat on Tuesday February 24, 2026 @08:39PM
(#47146203)
It's called rv: https://github.com/spinel-coop/rv