> There’s a reason that category of thinking exists. What's the reason? > But since GraphQL libs are now busy implementing caching What are you referring to?

> There’s a reason that category of thinking exists. What's the reason? > But since GraphQL libs are now busy implementing caching What are you referring to? You mean like https://github.com/graphql/dataloader https://github.com/graphql/dataloader ? > in top of non-cacheable POST requests, this argument is lost on them. I think caching/serving HTTP results is a bad paradigm. It makes sense if you're serving HTML for a content site or something like that, but doesn't make sense when you're serving an API.