3 ms·

All of this is possible with a jsonschema too. I agree that most people use GraphQL wrong because its impossible to use 'right'. Graphql 'solves' the trivial

by BLanen 3y ago

All of this is possible with a jsonschema too. I agree that most people use GraphQL wrong because its impossible to use 'right'. Graphql 'solves' the trivial while hinting towards a future of self-describing apis and anything in between. Users will hopefully find out that GraphQL never solved any actual problems. Actual problems(valdation, (actual)error-handing, cache-invalidation being the big one in the end like usual) are kept for the user as an exercise, like always. Their promises are always not explicit but implied so the tech-enthusiasts can pick it up. I remember an article here that was talking about how GraphQL would enable apis to discover eachother on the whole internet and learn to speak to eachother without human intervention. The main selling point in the beginning was so you don't have to query fields you don't actually need to keep data transfer to a minimum. A completely trivial feature for a json api. Even a JSON api with relations is just as possible and just as easy with a JSON api. Unlike GraphQL you don't have to pretend syntax was the issue.

satvikpendem 3y ago
> Actual problems(valdation, (actual)error-handing, cache-invalidation being the big one in the end like usual) are kept for the user as an exercise, like always As I mentioned elsewhere, Relay solves all of these problems automatically while people try to hack around their homegrown solution with React Query and the like. JSON Schema is tacked on as an afterthought to REST, not built in, so it's necessarily more hacky than REST.
- BLanen 3y ago
  Yes, Relay does a good job at many of these problems. Graphql SHOULD have been Relay. Graphql without Relay is almost just a syntax.
  - satvikpendem 3y ago
    True, I will agree with you on that, and I mean, Facebook uses GraphQL just as they intended it with Relay, what are they supposed to do if others just use it as a syntax instead?

by BLanen 3y ago

satvikpendem 3y ago

> Actual problems(valdation, (actual)error-handing, cache-invalidation being the big one in the end like usual) are kept for the user as an exercise, like always As I mentioned elsewhere, Relay solves all of these problems automatically while people try to hack around their homegrown solution with React Query and the like. JSON Schema is tacked on as an afterthought to REST, not built in, so it's necessarily more hacky than REST.

BLanen 3y ago
Yes, Relay does a good job at many of these problems. Graphql SHOULD have been Relay. Graphql without Relay is almost just a syntax.
- satvikpendem 3y ago
  True, I will agree with you on that, and I mean, Facebook uses GraphQL just as they intended it with Relay, what are they supposed to do if others just use it as a syntax instead?