if GraphQL told people that REST suck, people won't use it because their attachment to REST will make them more biased towards that, and it results in people finding every possible error they can to not use it. rather it solved a different set of problems and came with different drawbacks that made people more open to GraphQL as well. if today GraphQL told they are better than REST, there are a lot of people to agree that. you should've shown honest downsides and when will it be useful, when will GraphQL and REST have an upper hand over it, and so on.
if GraphQL told people that REST suck, people won't use it because their attachment to REST will make them more biased towards that, and it results in people finding every possible error they can to not use it. rather it solved a different set of problems and came with different drawbacks that made people more open to GraphQL as well. if today GraphQL told they are better than REST, there are a lot of people to agree that. you should've shown honest downsides and when will it be useful, when will GraphQL and REST have an upper hand over it, and so on.
I hesitated for a long time about the choice of the term "Component", and I am still hesitating to replace it with "Model". What do you think?
that's a good idea