Again, the problems you describe with REST are a limitation of your implementation, not of REST itself. GraphQL itself is built on top of REST via a single GET/POST query endpoint.

The difference between it and typical REST implementations is that the resource identifier and fields to return have been moved into a novel query syntax. However, the same result can be achieved with a typical REST endpoint combined with a sparse fieldset query parameter [1]:

    /users/123?fields=name,email,work.name,work.address

where "work" is a sub-resource in the same vein as GraphQL. The difference between this and GraphQL is purely syntactic:

    user({ "id": 123 }) {
        name,
        email,
        work {
            name,
            address
        }
    }

[1] http://jsonapi.org/format/#fetching-sparse-fieldsets