dlai

6 ms·

1. 1.▲
   by dlai 7y ago

   That video is definitely a great start. They should add that to the homepage. I was having a hard time comprehending all that in "Why Graphiti", that video explains it nicely.
2. 2.▲
   by dlai 7y ago

   I appreciate the effort. I think it is a bit of initial information overload having to read through tons of theory before getting to examples, which is why I skimmed through it and went to the examples. However the examples, did provide t
3. 3.▲
   by dlai 7y ago

   Not saying this has to exactly replace graphqL, but I'm struggling to understand the advantages and disadvantages over REST and GraphQL, or even how it tackles the problems graphQL is trying to solve. My understanding looking at the qu
4. 4.▲
   by dlai 8y ago

   One thing I do see that's missing (or maybe just not documented) is the power to specify the exact shape of the response. One of the power of GraphQl is allowing us to specify how much or how little of the result objects we want. For
5. 5.▲
   by dlai 8y ago

   My understanding looking at the code example is it turns a rest call into a services layer then maps it to GraphQL. I think this creates a bad convention of creating a service layer dependency on express where it's not needed. As a pro