While this is good, I'm astonished that this took so long, especially compared to Ruby On Rails. GraphQL was introduced 2 years ago, in the spring of 2015. And

While this is good, I'm astonished that this took so long, especially compared to Ruby On Rails. GraphQL was introduced 2 years ago, in the spring of 2015. And it's taken this long to get a CLI tool that can auto-generate some of the schema/setup? 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.)