#GraphQL is the worst fuck I had to deal with, and I dealt with hundreds of shitty APIs but this is just another hyped Meta product forced on devs that is over engineered to a point where all its conceptual advantages are obliterated by complexity.
@louis I've never used it. My main concern with graphql is that too many web frameworks have a quick 30 second "add graphql" switch and I'm worried that inexperienced devs might not understand the implications of letting the frontend query their DB like that. I'm not sure if this is truely a problem with GraphQL though,or if it is more a trouble of the way frsmeworks expose it.
@louis Haha, this experience mirror my worst fears. I've actually turned down job offers because I felt the ideas behind GraphQL seemed super sketchy and it made me doubt they knew what they were doing.
{
"errors": [
{
"message": "Query cannot be executed. The maximum allowed complexity for a query is 11000 but it was 20200. Simplify the query e.g. by setting lower limits for collections.",
"extensions": {
"contentful": {
"code": "TOO_COMPLEX_QUERY",
"documentationUrl": „…“,
"details": {
"maximumCost": 11000,
"cost": 20200
}
}
}
}
]
}
@louis@Jhelberg That however sounds like this particular GraphQL implementation is overblown. Not that agraphQL by itself is overengineered.
I looked at GraphQL first in the context of blogs about Sourcehut, and the examples there didn't look as crappy as yours. By far not.
My conclusion is that once again, tools are often neutral and it's our use of them that makes the difference. Or, sometimes it's the message, not the messenger.
Add comment