Before I go further, I want to clarify that I love GraphQL as a frontend engineer. It empowers me to... Tagged with graphql, webdev, react, javascript.

Dev.to is a community platform for developers, offering resources, discussions, and networking opportunities to empower individuals in their coding journey. Developers can learn new programming languages, frameworks, and tools, engage in discussions on best practices, and share their experiences with fellow developers to enhance their skills and grow their professional network.

GraphQL provides a lot of flexibility on the client side but this means that we cannot optimize as aggressively on the server. Traditional REST API is familiar to many engineers. It's one extra thing someone has to learn before they can be productive. There is an argument that we should just start off with GraphQL if that's ultimately where we want to get to.

Why I no longer use GraphQL for new projects

This is a perfect post for all GraphQL haters and I already see that the comments are also going in the same direction 🤦‍♂️
For me I gave it a try together with Apollo and Nestjs and I really begin to love it a lot. 
I totally understand that it can be a huge pain setting it from the ground up… but with the right tools it seems like a charm for me.
Am I wrong and its getting a huge pain longterm?!
Honestly, whats your opinion ?

I have been moving to using GraphQL and gRPC. Works great.

I wish there was a downvote button

As GraphQL gets older, the tools to get it up and running for every project become more available. People will start developing frameworks and better solutions for it. Then we will start using it more and more.
But taking a step back and looking at it… Facebook developed GraphQL spec because they needed to optimize their client for bad mobile connections. Do you have a platform as big as Facebook? You might not need GraphQL. Just go with a REST.
I’ve used GraphQL with PHP a couple of times and it did take a while (a month, and continuous development afterwards), but it’s so good because it forces me to think about the schema first, I get type safety and deferred loading of data.

Agree with the author about starting up a project with all whistles and bells on the server from the first day. it’s not against graphql, but for quickstart and understanding the needs in a progressive manner.