4 ms·
I don't like GraphQL due to the complexity. It's not JSON or YAML, and requires a lot of custom stuff on both ends. I'd like something like GraphQL, but built
by blagie 4y ago
I don't like GraphQL due to the complexity. It's not JSON or YAML, and requires a lot of custom stuff on both ends.
I'd like something like GraphQL, but built on standard data formats.
- mb7733 4y agoEvery graphql API I've ever seen returns JSON. It's definitely the standard. What are you referring to?
- habitue 4y agoI think they're referring to the query language itself not being json or yaml
- blagie 4y agoExactly. It's not just not-JSON, but it's obnoxious and hard to manipulate programmatically, on either end (client or server). That translates to a lack of tooling around it, an inability to write sane tooling, and difficulty interfacing in higher-order ways to things like interesting data stores. It's designed to be hand-written and parsed only with the official libraries.
- yencabulator 4y agoIt hasn't seen much outside adoption, you might enjoy the ideas behind Netflix's Falcor: https://netflix.github.io/falcor/ https://netflix.github.io/falcor/ You can think of it as larger-than-what's-downloaded dynamically-generated JSON object with internal pointers where you can ask to access wanted paths. (Sort of like GraphQL is a larger-than-what's-downloaded dynamically-generated non-JSON object.) One trick they use is that the path segments can also be objects, so `{from: 100, to: 200}` is a valid path segment, and this is how you build fancier query logic with in. https://youtu.be/hOE6nVVr14c?t=977 https://youtu.be/hOE6nVVr14c?t=977