This article is in desperate need of some editing. I’d love to know why he no longer uses MVC frameworks but he goes on tangents before he even begins. A thesis statement would be nice too.
Weird article. The author throws some stones at GraphQL, which was mostly designed to avoid over-fetching and multiple roundtrips, and presents his own solution as simpler and better, but without solving the issue solved by GraphQL.
This article is in desperate need of some editing. I’d love to know why he no longer uses MVC frameworks but he goes on tangents before he even begins. A thesis statement would be nice too.
Not to mention that the authors main reasoning is built on strawman arguments against specific frameworks rather than MVC as a whole.
Weird article. The author throws some stones at GraphQL, which was mostly designed to avoid over-fetching and multiple roundtrips, and presents his own solution as simpler and better, but without solving the issue solved by GraphQL.