Why not use GraphQL?

Re:Why not use GraphQL? by HeyHoJoe on Saturday November 07, 2020 @02:19PM (#25017887)

This is just going around in circles. “This thing is bad practise”. Ok, don’t do that thing. This is not an argument against rest or for graphql.

[ Parent | on HN ]

Re:Why not use GraphQL? by filoleg on Saturday November 07, 2020 @04:39PM (#25019745)

I think the point the parent reply is trying to make is not that you cannot follow good practices with REST and that you somehow magically get it with GraphQL. I think their point is that GraphQL makes it much easier for devs to follow good practices and with less resistance.

[ Parent | on HN ]

Re:Why not use GraphQL? by pookeh on Saturday November 07, 2020 @05:54PM (#25020481)

Put differently, Graphql gives good defaults out of the box, and REST bad defaults.

[ Parent | on HN ]

Re:Why not use GraphQL? by HeyHoJoe on Saturday November 07, 2020 @06:59PM (#25021140)

Apologies for being rude, but that’s just nonsense. What ‘good defaults’ does graphql give you?

[ Parent | on HN ]

Re:Why not use GraphQL? by dosethree on Wednesday November 11, 2020 @01:20PM (#25061080)

You can do a lot of the things that Graphql does bu just a regular old JSON HTTP API. It's just not automatic and you will have to choose your own conventions

[ Parent | on HN ]

Re:Why not use GraphQL? by pookeh on Monday November 09, 2020 @03:46AM (#25032687)

You no longer have to code data selectors explicitly for each endpoint.

[ Parent | on HN ]