3 ms·
GraphQL has nothing to do with graphs and caching GraphQL is an exercise in masochism. And it's not even a query language in the sense of SQL. It's just about t
by deckard1 7y ago
GraphQL has nothing to do with graphs and caching GraphQL is an exercise in masochism. And it's not even a query language in the sense of SQL. It's just about the worst named tech we currently use, IMO.
- hn_throwaway_99 7y agoYes, calling it a "QL" was a huge, huge mistake, judging by the amount of comments on HN and elsewhere asking questions that are clearly influenced by an understanding of SQL but are basically non-sequiturs in the world of GraphQL (e.g. "How do you do AND joins with GraphQL?"). I admit, I didn't read the article, but even it seems like (mostly) a non-sequitur to me based on the title. Minimizing network requests is one teeny part of why I like GraphQL, and do say "we don't need it because HTTP2" is completely absurd.