3 ms·
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.
by HeyHoJoe 6y ago
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.
- filoleg 6y agoI 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.
- pookeh 6y agoPut differently, Graphql gives good defaults out of the box, and REST bad defaults.
- HeyHoJoe 6y agoApologies for being rude, but that’s just nonsense. What ‘good defaults’ does graphql give you?