So you are saying to do a comparison, one should compare against a ‘vague spector’ rather than analyzing what has been presented as GraphQL to date???

And regardless, most of what has been presented still applies:

• additional layer
• difficult to cache
• multiple calls rather than a single call (see API Chaining)
• no rate limiting
• slow
• etc

The arguments still stand regardless of what method you use to return the resource.

Plus it breaks AOP principles by trying to combine the model and controller logic. Its just shitty programming when you can get better speed, scale and functionality through better programming.