I think my take on REST vs GraphQL is: most people want to have good docs, native clients, and helpful error messages. They probably care less about the technology backing any of these.
Hmm, I'd say: not necessarily. Both REST and GraphQL are mostly just specs, which (to my knowledge) don't define much in terms of documentation and error handling. It's mostly the tools around the specs that define how docs & error handling are done, which in turn drive quality.
-
-
REST is not even a spec, it’s an architectural style.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Ah I see what you mean by technology now. I guess what I mean is that graphQL feels like it "comes with" the tools & docs bc they're treated as first class citizens, hence in my head they're part of the technology. Which, like you said, is prob why they succeed.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.