[ram_rar]

Starting today in what scenario would RoR would be a better option than Next.js for building web app? Assuming one has to start from 0 -> 1 .

[Glyptodon]

I don't hate NextJS or anything, but I've never met a JS backend that I loved a whole lot compared to a conventional Rails one. They always turn out to be missing little details and trying to fill them in always like round hole square peg misalignment that just never quite ends.

[moojacob]

I’ve worked two summers on a Next.js app and Rails for a side project that I’ve spent 300 hours on. I would choose Rails if the interactivity could be made only with forms. Rails is simpler, opinionated, but a lot less powerful. But I was making a whiteboard which is super interactive I’d choose next.js. The con with Next.js is it’s just more complicated, some of my coworkers often shot themselves in the foot by not putting code inside useEffect

[philip1209]

I outline two in the article:

1. One-person software project

2. Complex enterprise app with lots of tables, like a vendor management system.

[taormina]

I mean, any scenario? I'm not trying to be snarky but server-side Javascript has always been a weird code smell from first premise. Now, when to use RoR vs a lighter-weight framework like Sinatra is a more interesting question, but it's about what you need out of the box.

[verisimilidude]

Server-side JS is fine, and actually very nice in some contexts. The language and runtime(s) have come a long way.

But anyone who tries it without really understanding JS is eventually going to have a bad time. It’s important to know how to work with the event loop, how to properly use promises, etc. Server-side JS is a lot more unforgiving than front-end JS when it comes to these concepts.

[prh8]

Almost all scenarios