Update GraphQL tagline for the AI era - #2361
Conversation
All the kudos goes to @bignimbus for mentioning this during today's working session.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Eager to get feedback on this! |
|
Love it! |
|
Feedbacks from the AI wg:
|
|
Love it! |
|
“API Language” doesn’t feel as clear or precise as “query language for APIs” to me. |
|
Awesome! |
|
src/pages/index.mdx has this too |
Updated in c668258 as well as a few codeblock examples. |
|
GraphQL is modern: ergonomic, attractive, introspective, type safe, expressive, version-less, self-describing, composable, network efficient, token efficient, easy to pick up, easy to debug, degrades gracefully, tightly specified, interoperable, capable of real-time, capable of progressive responses, vendor-neutral, cross-platform, community-driven, has strong backwards compatibility guarantees, and a large and highly engaged community, ... GraphQL is glorious. To me, "the API language for humans and agents" says little of this. It feels bland, vague, and like it's simply attaching to the current trend without really saying anything. I'm not even sure what "API language" means - is that term defined somewhere? It feels like you have to already know what GraphQL is to realise it encompasses many of the possible meanings of the seemingly ambiguous1 phrase? I'm clearly in the (vast) minority on this given the number of approvals above, so don't let me stop you merging it, but I personally feel like "The query language for modern APIs" is stronger and more descriptive than "The API language for humans and agents"2. But I'm no marketing expert so I'll defer to those who know better than me. 🤷♂️ Footnotes
|

All the kudos goes to @bignimbus for mentioning this during today's working session.