3 ms·
All four points are valid criticism of Relay. Point 1 and 2 especially and the verbose structure of connections is why we decided to offer two endpoints to your
by sorenbs 10y ago
All four points are valid criticism of Relay. Point 1 and 2 especially and the verbose structure of connections is why we decided to offer two endpoints to your project on graph.cool - one that supports all the relay conventions and one that feels much nicer to use.
We decided very early on to use Relay for our main frontend (a dashboard similar in complexity to Parse.) It's probably one of the largest open source projects using relay atm, so maybe having a look at that can be helpful https://github.com/graphcool/dashboard https://github.com/graphcool/dashboard
In summary we have found that the benefits Relay offer makes up for the quirks and complexity Relay currently forces you to learn. Hopefully Learn Relay can help more people get up to speed faster.
- happyslobro 10y agoOpen source, hosted as a service. The world needs more of this. Major props for having the courage and wisdom to open source your product. My weekend is packed already, but I'll be back to check this out. I'm just starting to take a second look at GraphQL and co. Last time I looked at it, the conclusion was "extremely interesting, but too alpha for work." Did you notice that Facebook's ad / business manager uses a mix of GraphQL, REST, and RPC over HTTP POST? Watching the traffic in major production applications is fascinating.