3 ms·
Ruby on Rails for everything, front and back end. There is no advantage to using front-end frameworks such as React for most apps that I have seen. I could only
by mosselman 9y ago
Ruby on Rails for everything, front and back end. There is no advantage to using front-end frameworks such as React for most apps that I have seen. I could only imagine something like Slack is nicer to build with something like React/Ember/Vue.js/whatever.io but for most applications Rails has got your back.
- octalmage 9y agoI've been using Rails and React for a couple of projects, one using Rails API mode with a separate React front end, and one using react-rails. I'd argue that with webpacker built in, there's no reason not to use React. You get server side rendering built in, automatic production builds and hot reloading. It's a great Dev experience out of the box with no setup. Of course this depends on your frontend and your goals. If you're just going to have a minimal static frontend, then maybe React isn't a great choice. Although I'd still use React and just render it to static HTML at build time.