←back to thread

153 points michaelanckaert | 2 comments | | HN request time: 0.411s | source
Show context
say_it_as_it_is ◴[] No.23486965[source]
Where are the GraphQL lessons learned? The author hasn't even implemented a solution with it yet, but that hasn't stopped him from declaring it to the world. I don't find an announcement useful.

Maybe GraphQL adopters aren't sharing their experiences with it in production because they're realizing its faults? People are quick to announce successes and very reluctant to own, let alone share, costly mistakes. Also, people change jobs so often that those who influence a roll-out won't even be around long enough for the post-mortem. GraphQL publicity is consequently positively biased. If the HN community were to follow up with posters who announced their use of GraphQL the last two years, maybe we can find out how things are going?

replies(2): >>23487501 #>>23487793 #
1. gbear605 ◴[] No.23487793[source]
The reason this post was written was for users of Sourcehut, especially for people writing to its API. This post isn’t particularly relevant or explanatory for other audiences, but I don’t think it’s supposed to be so that’s fine.
replies(1): >>23488800 #
2. say_it_as_it_is ◴[] No.23488800[source]
I understand what you mean. That makes sense.