3 ms·
Sorry, I'm confused: what do you mean by "migrated a 5 year old codebase from Rails to React"? What are you using as your backend?
by enraged_camel 10y ago
Sorry, I'm confused: what do you mean by "migrated a 5 year old codebase from Rails to React"? What are you using as your backend?
- problems 10y agoJust one of the many ways that modern Javascript baffles me - people pretend the client and server are equivalent.
- atoko 10y agoYou can still render placeholders from the server and fill these in with React
- mehwoot 10y agoThe more technical details you include the more people pick up and discuss minute technical details instead of the point of what I was trying to say, which is that my experience with a large codebase was these modern javascript tools have solved a lot of problems we had. If you want all the gory details here they are: it was a Rails 3 app using Postgres and Elasticsearch that we migrated to React + node.js + webpack + babel, elastic search as the data store and using Keystone.js for backend data manipulation (which uses mongodb). Rails was indexing its data in Elasticsearch already so we could start serving data through node.js immediately without having to migrate all the data backend, which is being slowly moved to keystone.js.
- grosbisou 10y agoMaybe they hardcoded the data in the views. Might be the cool way to do it soon enough.
- mehwoot 10y agoSorry I should have clarified. React + node.js. We need the option of HTML being sent to clients so React + Rails wasn't an option