3 ms·
> but the HATEOAS detail ends up having no practical value and creates more problems than the ones it solves. Only because we never had the tools and resources
by troupo 1y ago
> but the HATEOAS detail ends up having no practical value and creates more problems than the ones it solves.
Only because we never had the tools and resources that, say, GraphQL has.
And now everyone keeps re-inventing half of HTTP anyway. See this diagram https://raw.githubusercontent.com/for-GET/http-decision-diagram/refs/heads/master/httpdd.fsm.png https://raw.githubusercontent.com/for-GET/http-decision-diag... (docs https://github.com/for-GET/http-decision-diagram/tree/master/doc https://github.com/for-GET/http-decision-diagram/tree/master...) and this: https://github.com/for-GET/know-your-http-well https://github.com/for-GET/know-your-http-well
- motorest 1y ago> Only because we never had the tools and resources that, say, GraphQL has. GraphQL promised to solve real-world problems. What real world problems does HATEOAS addresses? None.
- troupo 1y agoGraphQL was "promising" something because it was a thing by a single company. HATEOAS didn't need to "promise" anything since it was just describing already existing protocols and capabilities that you can see in the links I posted. And that's how you got POST-only GraphQL which for years has been busily reinventing half of HTTP