GraphQL, a query language for APIs, has been criticized for being incompatible with HTTP caching. However, this criticism lacks nuance and fails to consider the various ways caching can be implemented in GraphQL, including client-side caching, server-side caching, and application-level caching. While GraphQL's transport-agnostic nature makes it challenging to utilize HTTP caching semantics, the lack of a GraphQL over HTTP specification is a significant limitation. Nevertheless, there are alternative approaches to caching in GraphQL, such as using persisted queries or implementing caching middleware for clients. As the field continues to evolve, we can expect to see a mix of GraphQL-specific caching implementations and standardized HTTP caching mechanisms. GraphQL's focus on real-time data and authenticated APIs means it may not be the best fit for applications that require long-lived data served through an HTTP API. Ultimately, understanding the trade-offs and limitations of caching in GraphQL is crucial for building scalable and performant APIs.