3 ms·
If you go down the GraphQL path be aware you are trading the simplicity, flexibility and universality of HTTP, which you can debug via cURL, to a custom protoco
by iamleppert 8y ago
If you go down the GraphQL path be aware you are trading the simplicity, flexibility and universality of HTTP, which you can debug via cURL, to a custom protocol and fat client owned by Facebook. It isn’t even an open standard. The last time Facebook tried to make HTML better we got FBML, remember that?
Be wary of tech that promises to solve all your problems that you yourself don’t understand and haven’t solved. You’re going to end up with at best another set of problems.
- nicolasd 8y agoThat's not true. "GraphQL requests" are _just_ POST requests with a JSON that contains "query" and "variables". So it's not the request itself that is not debuggable, but maybe the query interpreter on your backend with the framework you're using.
- iamleppert 8y agoHave you ever seen one? They are impossible to formulate with simple tools like curl on the command line. So my original point stands.