I think it's a marketing problem. GraphQL can easily sound like "Give the entire schema to your users and let them decide what to query for". If you look at var

I think it's a marketing problem. GraphQL can easily sound like "Give the entire schema to your users and let them decide what to query for". If you look at various GraphQL supportive websites, that is a common anthem. You don't get that marketing from REST. REST says "decide what's good for them". Obviously you can do either in either. But i definitely think the marketing is world's apart. So when people come to a problem, if they are not super strong in their understanding of what will be a good solution, they generally implement what the platform markets.