Post Ac4QsRYkBjVFqfV6Aa by pmidden@fosstodon.org
(DIR) More posts by pmidden@fosstodon.org
(DIR) Post #Ac4IPwhuVFcAQ8gkBk by louis@emacs.ch
2023-11-22T15:07:45Z
0 likes, 0 repeats
#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.
(DIR) Post #Ac4IYC7R5QeyXHYqQ4 by schizanon@mas.to
2023-11-22T15:09:18Z
0 likes, 0 repeats
@louis if you use a hashtag to complain about something, you have only yourself to blame when people who follow that hashtag tell you you are wrong
(DIR) Post #Ac4QsRYkBjVFqfV6Aa by pmidden@fosstodon.org
2023-11-22T16:42:35Z
0 likes, 0 repeats
@louis I haven't used it in depth and have no real opinion on it yet. Would love to hear some examples of this shittiness.
(DIR) Post #Ac4TvfFa2f7h2clS6q by Jhelberg@mastodon.social
2023-11-22T17:16:41Z
0 likes, 0 repeats
@louis any literature on that?
(DIR) Post #Ac4XtoaUkqfjEov8y0 by nthcdr@emacs.ch
2023-11-22T18:01:12Z
0 likes, 0 repeats
@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.
(DIR) Post #Ac4g7JGWnzKbmXWjzs by louis@emacs.ch
2023-11-22T19:33:20Z
0 likes, 0 repeats
@Jhelberg I have not yet managed to put my personal experiences into literature.
(DIR) Post #Ac4gRWsnszSVo64V7I by louis@emacs.ch
2023-11-22T19:37:00Z
0 likes, 0 repeats
@Jhelberg But here is a taste of it:```{ "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 } } } } ]}```
(DIR) Post #Ac4pH7W0FNJJp1WBeq by djrmarques@emacs.ch
2023-11-22T21:15:57Z
0 likes, 0 repeats
@louis I actually use it at work. Can't say I love it, but it seems convenient to query data in a graph structure no (which is our case)?Although I will say that took me some time to actually get started with it
(DIR) Post #Ac5rVD36rXus6coFXs by timthelion@emacs.ch
2023-11-23T09:15:36Z
0 likes, 0 repeats
@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.
(DIR) Post #Ac85gm3apeVlXZMdJg by Jhelberg@mastodon.social
2023-11-24T11:03:58Z
0 likes, 0 repeats
@louis hm, that is a nuisance. You're not on the server-code I assume? Query-complexity sure is a worry in graphql, but on the other hand, most api's end up having a single complexity regardless of the complexity of the request. Graphql makes it possible to match the complexity of resolving the request with the complexity of the request itself. Of course there are upper bounds, in REST these are enforced by not being available.
(DIR) Post #AcBtrVGFCJcVogTFZI by holgerschurig@emacs.ch
2023-11-26T07:10:20Z
0 likes, 0 repeats
@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.