I’m having a bit of trouble getting the point here, this is more sort of just a passing thought I guess. But yeah, like the article ends with, querying with graphql from the front end, and using loaders from Remix are 2 choices for different situations where they’re ideal. (Unlike the superlative title implies)
It's like they are designed for completely different use cases.<p>Graphql is designed to be flexible for when you want to expose your data to many clients who may be other teams and need different models of the data.<p>Obviously, if you just need a simple consistent API, there's no need for all the extra complexity.
If I were using Remix, I'd probably trigger GraphQL queries from route loaders, one doesn't really obviate the other. Yes, there are challenges with using GraphQL well, but there's no inherent tension between it and the loader approach.
this is so bizarre? I use GraphQL with Remix in my loader. It's a great combination. 7ms response from SQL. I can't understand the article. Sorry this person doesn't understand GraphQL nor Remix. might be AI generated
Conway's law.<p>REST/GraphQL is the result of different teams/orgs working on frontend and backend.<p>Backend-for-frontend/Remix is the result of the same team working on frontend and backend.