My story with learning and using GraphQL is a bittersweet one, I went from "What does this button do?" 
to "WOOT WOOT"
Why did you start using GraphQL? If you don't why not?
Obinna Ekwuno
Posted on
What do you think about GraphQL? Who's using it? Love it, hate it? Tell me why?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (10)
I only came across GraphQL when I was looking at Gatsby. From the few interactions, it looked quite interesting for me because I think its pretty easy to understand though I dont know much about it. I promised myself that I will actually purpose to get into its depth and understand how it works. You can share any resources if you have.
I haven't looked into it primarily because I'm worried about the learning curve and how much I'd get out of it for how much I'd have to put in.
What tools do you build with currently?
If I was to use GraphQL I'd probably look into using it with Apollo+Angular and NestJS. Currently just build REST endpoints and NGRX is keeping everything pretty solid, hence why moving doesn't seem necessary.
I like it too much. I think we are faster when it's about basic crud operations. Also, it's easy to add resolvers for specific bussiness logic. The only thing I dont like too much is that it brigns us a lot of flexibility in the frontend, so we need to be careful to mantain a clean code and don't abuse service calls
oh, some would argue that the flexibility to the frontend is a good thing.
I love it! Fetching just what the user needs and nested queries are my favourite features. The typescript tools built around it is bliss, Graphql codegen for example.
The only reason I have procrastinated in learning it is because I am not a fan of using a string for a graphql query in a function to call that query.
An example being:
oh, but then I would advocate that it's a small price to pay for the value you get back.