4 ms·
yes but we can build our own query tools, for ex. Im using `$ so graphql vs sql` and such terminal commands more and more these days
by alexalx666 4y ago
yes but we can build our own query tools, for ex. Im using `$ so graphql vs sql` and such terminal commands more and more these days
- marginalia_nu 4y agoOh yeah, this is primarily a problem for Google. They're sort of stuck being chased by the shadow they cast. I've had very little problems cutting through the SEO spam running an independent search engine, but then I don't shape traffic like they do.
- hn_throwaway_99 4y agoSorry, unrelated, but your comment hit a pet peeve of mine. I love GraphQL, and I think it has a number of features that make it better and more usable for most APIs than a RESTful interface. The thing I despise about GraphQL is they put "QL" in the name, so legions of software developers think that it is somehow comparable to SQL, or somehow is a generic query language for data. GraphQL has absolutely nothing to do with SQL. Comparing "GraphQL vs SQL" is like comparing "HTML vs Java".
- alecbz 4y ago> somehow is a generic query language for data. In what sense is GraphQL not a generic query language for data?
- 8n4vidtmkvmk 4y agobecause it's not? it's got no "where" clauses or transforms built in and anything of the sort had to be custom built. you can't query any data in the database, only what the API chooses to expose. it's anything but generic. even pagination isn't standardized
- hn_throwaway_99 4y agoGraphQL is a format and contract for exposing APIs, just like REST is a structure for exposing APIs, just like SOAP is a format and structure for exposing APIs, just like gRPC is a format for exposing APIs. Those are all the right analogies for comparing GraphQL. GraphQL doesn't say anything about how the underlying data is queried - at the end of the day it's just a bunch of resolver functions that you can implement however you want.
- deleted 4y ago[deleted]