News for hackers. Stuff that matters.
Re:How it feels to learn JavaScript in 2016 by enraged_camel on Tuesday October 04, 2016 @09:52AM (#12635478)
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?
Re:How it feels to learn JavaScript in 2016 by problems on Tuesday October 04, 2016 @10:30AM (#12635786)
Just one of the many ways that modern Javascript baffles me - people pretend the client and server are equivalent.
Re:How it feels to learn JavaScript in 2016 by mehwoot on Tuesday October 04, 2016 @06:49PM (#12640247)
The 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.

Re:How it feels to learn JavaScript in 2016 by atoko on Tuesday October 04, 2016 @11:36AM (#12636297)
You can still render placeholders from the server and fill these in with React
Re:How it feels to learn JavaScript in 2016 by grosbisou on Tuesday October 04, 2016 @11:27AM (#12636236)
Maybe they hardcoded the data in the views. Might be the cool way to do it soon enough.
Re:How it feels to learn JavaScript in 2016 by mehwoot on Tuesday October 04, 2016 @06:43PM (#12640219)
Sorry I should have clarified. React + node.js. We need the option of HTML being sent to clients so React + Rails wasn't an option