They adopting it because it saves them time. REST is all fun and games until a) you have a rich data model that all of your functional modules subset and b) you have aggregation (joins).
Since decent documentation (not just swagger endpoints but the real thing focused on business tasks rather than code) could only be found in thick software engineering books and million-dollar guys blogs, you need your backend developer pretty much every time you need to fetch something from API.
And this where GraphQL steps in. It also almost always wins over REST on slow networks because it can fetch just what you need at the moment.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
They adopting it because it saves them time. REST is all fun and games until a) you have a rich data model that all of your functional modules subset and b) you have aggregation (joins).
Since decent documentation (not just swagger endpoints but the real thing focused on business tasks rather than code) could only be found in thick software engineering books and million-dollar guys blogs, you need your backend developer pretty much every time you need to fetch something from API.
And this where GraphQL steps in. It also almost always wins over REST on slow networks because it can fetch just what you need at the moment.