I think it is fair to say that React and RoR are serving the same needs. Obviously the two approaches are very different, mainly because they are from different eras.
In many ways RoR is still ahead compared to React, and ease of getting started + tooling like you mention is one of them.
Expo and create-react-app is making good progress towards making this more seamless and we hope graphql-up with time will be able to solve the last missing piece, namely schema generation and migrations.
If you'd like to chat about RoR vs React/GraphQL and especially wider adoption by agencies and companies my email is [email protected]. Also - let me know if you are going to GraphQL Europe[1] - I'd love to meet.
Whoever asked that "real" question is confused. They're orthogonal.
These last 2 years, a lot of my clients have been asking me, "Should we switch to React/GraphQL?" And I've done one big project with GraphQL, in the spring of 2016. And I was amazed at how much I had to hand code, especially compared to Ruby On Rails.
In 2004, Ruby On Rails was born with these kinds of CLI tools. Indeed, Ruby On Rails pretty much established our modern ideas of how much a framework should do for us.
A CLI for GraphQL certainly makes the React eco-system more competitive with Ruby On Rails, but I am astonished that it took this long.
(PS: I am aware that React and Ruby On Rails are not strictly competitors, since you can use them together to create software/website. Nevertheless, "Should we use Ruby On Rails or React?" is a real question that I've been asked several times over the last few years.)