3 ms·
Article doesn't loads for me. Whatever is said, the answer is simple. REST was meant to be used by other applications in a not yet known way, and many where cla
by madmaniak 8y ago
Article doesn't loads for me. Whatever is said, the answer is simple. REST was meant to be used by other applications in a not yet known way, and many where claiming REST is a "best practice" for API of YOUR single page application. It led to doing the same thing in a huge scope twice - selecting, modelling, and preparing for view of data, maybe even more. So we didn't use the context of the query which already shapes the data. GraphQL does. But GraphQL sucks in other way - as it adds unnecessary querying language (which already exists on the backend and it's for sure more powerful), and it makes a query on the frontend which is a security issue (which you can limit on the backend, but it's just a consequence of this mistake and still leaky).