GraphQL folks keep on with the GraphQL vs REST narratives, rather than a REST and/or GraphQL narrative lately with a recent burger meme/narrative. Continuing to demonstrate their narrow view of the landscape and revealing the short-lived power of an adversarial approach to community building. I get why people do this because they feel they are being clever, and that the click response from the echo chamber re-enforces it, but ultimately, it is something that won’t move the conversation forward, but it does get them kudos within their community — which is what many of them live for.
I’ll start with the usual disclaimer. I actually like GraphQL and prescribe it as part of my API toolbox. However, rather than a REST vs GraphQL approach, I sell it as REST and GraphQL, depending on the developer audience we are trying to reach with our efforts. Whether or not you use GraphQL on your platform is completely based upon knowing your developers and working with a group that understands the resources before offered — something the GraphQL community continues their failure to see. Also, their adversarial marketing tactics have lost me several GraphQL projects in government because it comes off as being a trend and not something that will be around very long. https://goo.gl/a44gwc #DataIntegration #ML
