3 ms·
I'd stick with rails unless you have a complex front-end where UI responsiveness is of the essential (i.e., highly graphical-interactive). React is many levels
by insane_dreamer 4y ago
I'd stick with rails unless you have a complex front-end where UI responsiveness is of the essential (i.e., highly graphical-interactive). React is many levels up in terms of complexity.
- pcthrowaway 4y agoRails and React are doing completely different things in the stack; I don't understand this argument (having worked with both, but never getting good at Rails) React is purely about managing the frontend and user interactions. Many apps are very heavy on this. For a lot of things I've built, I think Rails would have been overkill. Even for ones that use a database, I find node.js/express/prisma much easier to work with (until you get into migrations). Activerecord's story around migrations is the best I've used. But for an MVP you don't really need to worry about that.