Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderTo be honest, I find graphql syntax really weird. What you get back is json, why not make the query language json itself? So all the existing json processing tools on the frontend just work. With the weird syntax, now you need a parser and checker, and you need to write some boilerplate for doing mutation syntax. There’s a reason why everyone and their dog invented ORMs. So you could live in an object world and everything would just work…
We've found much to like about GraphQL, but it's a minor annoyance that most GraphQL-based web services only accept POST requests (not also GET requests) and treat white-space in the query as meaningful. These little factors make it harder to run ad-hoc queries by curl/httpie/etc or in a web browser. Will have to give this tool a try to see how well it fits for quick, little debugging of GraphQL endpoints.
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 376
- Total comments
- 28
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2018-08-07 | Show HN: Graphqurl: curl for GraphQL with autocomplete, subscriptions, GraphiQL | alberteinstein | 3 | 0 |
| 2018-08-10 | Show HN: Curl for GraphQL with autocomplete, subscriptions and GraphiQLFirst breakout · Best thread | wawhal | 246 | 20 |
| 2021-01-05 | Graphqurl: Curl for GraphQL, with Autocomplete and SubscriptionsLatest 20+ point return | jaredwiener | 127 | 8 |
