DEV Community

Discussion on: Why I no longer use GraphQL for new projects

Collapse
willvincent profile image
Will Vincent

I hate graphql... full stop.

The client side should never need be so intelligent about the data as is necessary with graphql. Its a terrible pattern imho.

Collapse
nickcoad profile image
Nick Coad

There are many usecases where clients can benefit from the added flexibility. No single style of API will be perfect for every purpose, but making statements like that just makes you look a little narrow minded to be honest. Choose the right tool for the job, sometimes that's GraphQL, sometimes it gRPC, sometimes it's REST, and sometimes it's something altogether different.

Collapse
willvincent profile image
Will Vincent

I never suggested there was ever a single api style that's perfect for every purpose. But GraphQL is shit, and rarely the right solution for MOST use cases where it's mistakenly employed.

As for how open or narrow minded I am - conveniently, your opinion on it doesn't affect me whatsoever 👍

Thread Thread
conantonakos profile image
Constantine Antonakos

It's clearly not shit, many teams big and small have invested in it (ex: Facebook). Please back up your claims, and we can have a constructive conversation. :)