Closed stevefan1999-personal closed 6 years ago
and it precedes the time when the "GraphQL" of FB came out, so I think there will be a brand name issue?
@stevefan1999 I don't think it a problem since:
GraphQL
is not a trademarkIt's almost impossible to come up with a meaningful name that was never used before.
@stevefan1999 Did I answer your question? Can I close this issue?
It's okay, just thinking that why this "GraphQL" doesn't really do with graphs at all🤣Now I've found the true "GraphQL".
"GraphQL" doesn't really do with graphs at all
Actually, it means that your type system is a graph and you query it. So the query is a set of instructions on how to traverse a type system graph and generate a response tree (JSON). You can visualize type system graphs using this tool: https://apis.guru/graphql-voyager/ The uniqueness of a graphql is that it manages to wrap complex algorithms in the simple syntax that approachable by an average developer without CS degree.
Okay, now this paper really does describe GraphQL😍
@stevefan1999-personal You can watch a talk from one of the authors here: https://www.youtube.com/watch?v=oNDmVLRKo_M&index=6&list=PLn2e1F9Rfr6lOTXAxwZDlukTVpBxyxeur
https://sites.fas.harvard.edu/~cs265/papers/he-2008.pdf
Because the novel language of the paper is also called "GraphQL", and it precedes the time when the "GraphQL" of FB came out, so I think there will be a brand name issue?
BTW the paper is pretty well written.