I enjoyed the article. I realize you're just the messenger, but the REST v GraphQL bullet points are one sided. They just took things that are pain points in REST and ignored calling out any of the GraphQL pain points.
There's a more balanced approach to comparing REST and GraphQL.
Totally! Nothing is truly black and white in the world of software development. I'm just getting into GraphQL so I'll likely experience some of the pains later on but am enjoying it thus far.
I enjoyed the article. I realize you're just the messenger, but the REST v GraphQL bullet points are one sided. They just took things that are pain points in REST and ignored calling out any of the GraphQL pain points.
There's a more balanced approach to comparing REST and GraphQL.
Totally! Nothing is truly black and white in the world of software development. I'm just getting into GraphQL so I'll likely experience some of the pains later on but am enjoying it thus far.
Here's a great article describing some of the GraphQL pain points I've read before.
blog.logrocket.com/5-reasons-you-s...