[contravariant]

Having more implementations of GraphQL APIs for various backends is tremendously useful for data integration using schema stitching / federation / remote schemas. And even without that it provides a uniform way to address many types of data stores.

Also the term 'retrofit' is a bit odd for an API, as there is no canonical backend, so there are only retrofits in that sense.

[philliphaydon]

It's not odd at all. If you have existing datastore(s) and APIs, and you try to add GraphQL on top of it. You're trying to retrofit it.

> add (a component or accessory) to something that did not have it when manufactured.

GraphQL doesn't magically just tie into a datastore and allow you to query it.

In most cases, adding GraphQL just add's another layer of complexity and doesn't solve any existing problem for people.

I'm not saying GraphQL is bad. It's just massively miss/over used now.