31–40 of 94 posts
Earlier quoted context omitted.
Fellow curmudgeon, I give you an upvote. SPARQL is a more elegant tool from a more civilised time.
that's awesome -- y'all are like the tech version of the Mad Max War Boys. sacrificed yourselves betting on the wrong tech. witness me!
Earlier quoted context omitted.
GraphQL isn't a query language, it's an API protocol language. Big difference.
From the website: "GraphQL is a query language for your API"
Earlier quoted context omitted.
SPARQL demands a certain data model (triple stores). Also, everything about it smells like ivory-tower academic snobbery + ultra-large-enterprise crap. GraphQL does neither.
GraphQL also demands a certain data model. Just that it is not standardized. And no, RDF/XML is not the only representation for SPARQL. It can deal also with JSON.
Great. Another solution for an already-solved, already-standardized query API language (SPARQL).
I recommend this talk to see what both technologies can still "learn" from each other - https://youtu.be/LUF7plExdv8 . I don't think SPARQL or GraphQL completely replace one another.
Earlier quoted context omitted.
Well it is a query language, QL stands for query language.
The name doesn't make it so. It defines a syntax and a single operator (nesting), but nothing else. You can't use it to "query" arbitrary data sources in the sense that other query languages such as SQL do, since there are no operators, functions, subqueries/arbitrary joins etc. It's an alternative to REST, not SQL.
Earlier quoted context omitted.
SPARQL demands a certain data model (triple stores). Also, everything about it smells like ivory-tower academic snobbery + ultra-large-enterprise crap. GraphQL does neither.
GraphQL also demands a certain data model. Just that it is not standardized. And no, RDF/XML is not the only representation for SPARQL. It can deal also with JSON.
Earlier quoted context omitted.
Generalization of Hanlen's razor: Never attribute to malice what can be explained by laziness/greed/stupidity. FB has GraphQL stable and doing exactly what they want it to do. Now they can pass it off to a foundation for maintenance and blame without having to pay out of pocket.
GraphQL isn't a system per-say, it's a spec and many tools around it. Putting the spec in a foundation (with a few of those tools) gives the entire community certainty about the direction of the project. Hopefully that spurs more people outside of FB to commit to GraphQL. The existence of the foundation is orthogonal to FB's internal investment and usage of GraphQL, which was and will continue to be significant.
Right pronunciation, but it's Latin. :)
Earlier quoted context omitted.
GraphQL also demands a certain data model. Just that it is not standardized. And no, RDF/XML is not the only representation for SPARQL. It can deal also with JSON.
GraphQL has no demands on your data model. You can do whatever you want behind the schema you provide to client apps
Earlier quoted context omitted.
GraphQL also demands a certain data model. Just that it is not standardized. And no, RDF/XML is not the only representation for SPARQL. It can deal also with JSON.
No, it doesn't, it is agnostic. There's an adapter for every major database out there. Oh, yeah, graphql also has momentum and strong adoption, unlike SPARQL.
Great. Another solution for an already-solved, already-standardized query API language (SPARQL).
SPARQL demands a certain data model (triple stores). Also, everything about it smells like ivory-tower academic snobbery + ultra-large-enterprise crap. GraphQL does neither.