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.
Put differently, Graphql gives good defaults out of the box, and REST bad defaults.
Apologies for being rude, but that’s just nonsense. What ‘good defaults’ does graphql give you?
You no longer have to code data selectors explicitly for each endpoint.
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