[quonn]

Can you expand on this? Is this a generic criticism of GraphQL? Apollo server? Client? And what do you mean by opposite track?

I really like GraphQL but agree that it‘s not trivial to implement well.

I also think it recently became a bit less relevant for web applications (React server components come to mind) but it‘s still very useful for some web apps, mobile apps and generally for designing nice APIs.

[Aeolun]

I think he takes issue with the theoretically infinite cost of a graphql query.

[dudul]

Maximum complexity control is a thing though.

[AtNightWeCode]

We use GraphQL a lot for static content. Most content on modern webs should be static, or at least deterministic. What I am saying is that GraphQL should not be used at runtime to do these dynamic magic queries, which is the key feature in Apollo.

[nawgz]

> Most content on modern webs should be static, or at least deterministic

What does this even mean?

> What I am saying is that GraphQL should not be used at runtime to do these dynamic magic queries, which is the key feature in Apollo.

What does this even mean?

How are you defining "dynamic magic" and "deterministic content"? GraphQL sends a query to a server that resolves it into the requested data. Is it not true that if you plug this into something like PostgreSQL via Hasura, you naturally have "determinism" in the same way Postgres offers it?

Please, expand, I have no idea what you're saying and I'm a full time web guy