4 ms·
What's the benefit of moving from Rails to Node and React productivity-wise? On the backend side, Rails comes with an ORM, authentication, templating system and
by neurostimulant 6y ago
What's the benefit of moving from Rails to Node and React productivity-wise? On the backend side, Rails comes with an ORM, authentication, templating system and many more out of the box, while on Node you'll need to mix and match a bunch of 3rd party libs or roll your own, which might be a good thing depending on your priorities but certainly kills productivity. On the frontend side, you can always use react with rails backend, but developing traditional template-based ui is usually faster than developing a react app and you can take advantage of rails templating/rendering feature to speed up development.
- mattmanser 6y agoEven in mid-sized projects there's usually one or two pages with sufficiently complicated front-ends that it's worth having something like React in your toolbox, though it might be Vue or Svelte. You don't have to make the whole app a SPA to use these tools. You can just use it in those few pages that really need it.
- joelbluminator 6y agoMeh, put React into your build, maintain the thing, make the website download and parse React - all that just for one page? Better be a damn dynamic page. I wouldn't do it even if it's a big form with some dynamic fields.
- emteycz 6y agoIt's very easy to load React only on the page that needs it. Use dynamic ES module import, or link the standalone builds only on the pages that use it. Alternative like Preact is very small and can be easily (pre)cached on the client side.