4 ms·
Ultimately GraphQL is popular because the query ergonomics fit well with the component architecture everyone is using these days, and once you're familiar with
by andrewingram 7y ago
Ultimately GraphQL is popular because the query ergonomics fit well with the component architecture everyone is using these days, and once you're familiar with it you can be extremely productive.
- dominotw 7y agosorry not a frontend dev, where can i get basic info about 'component architecture'
- hawkice 7y agoHe's talking about the recommended use of things like React or Elm. React will probably have the basic info that ties it to GraphQL the closest, given the creators.
- hmcdona1 7y agoModern SPA frameworks are usually built on components. You can combine components to define a tree of elements that represents your UI. This pattern is also often referred to as a Declarative UI pattern. GraphQL works well with declarative UIs, because you can define fragments and combine them to create queries that best match the data the current set of components you are loading require. In this way, it's flexible in a way REST isn't (at least typically) and syncs well with Declarative UIs. I can't speak to datalog though.
- rhizome 7y ago>GraphQL is popular because the query ergonomics fit well with the component architecture everyone is using these days Were they using that architecture prior to moving to GraphQL, or did the tail wag the dog in most cases?
- andrewingram 7y agoI can't speak for everyone, but in my case it's "yes". I'd also be fairly comfortable claiming that there are a lot more people using component architectures (React, Vue, Elm, Ember and Angular) than are using GraphQL.
- fulafel 7y agoDo you feel GraphQL is better than Datalog here?
- JMTQp8lwXL 7y agojQuery, for its time, fit well its architecture and those familiar with it were extremely productive. Doesn't necessarily mean something is a great paradigm.