And let me add that no one actually does REST, because it's nonsensical. It's just HTTP.

Reply to this note

Please Login to reply.

Discussion

Yes, but people do a pattern using convoluted pathnames that looks cool but it's incredibly inefficient and awkward for both clients and servers.

An HTTP ("REST") API is certainly no more wasteful than GraphQL.

If done right, it's literally just pushing bytes over the wire, whereas GraphQL at the very least involves JSON parsing, comparison, reconstruction, and serialization.