3 ms·

I agree with the article. Fortunately, REST is dead. I'm fully confident that in 5 years, newcomers to web development will simply learn GraphQL. I realize tha

I agree with the article. Fortunately, REST is dead. I'm fully confident that in 5 years, newcomers to web development will simply learn GraphQL. I realize that's a strident statement, but I really believe that. It is basically a restrictive implementation of RPC, which captures the reality that clients often need to ask for follow up data based on the result of a query. There are a couple needs that don't have fully baked solutions yet, but it's already extremely handy. It reminds me of what BEM did for taking the decision fatigue out of writing CSS.

camus2 9y ago
> newcomers to web development will simply learn GraphQL. I doubt it. Newcomers are supposed to learn HTTP. When one knows HTTP, one mostly knows REST. GraphQL is not a replacement for REST, it's a query language on top of REST. It's a useful tool to fetch object graphs but REST is not going away anytime soon. GraphQL doesn't deal with security, caching and other issues solved with REST for instance. GraphQL also pushes a lot of complexity toward both the server and the client. On the server,it's an ORM on top of whatever ORM developers are already using.