3 ms·
> not understanding how web 1.0 worked and really groking REST/HATEOAS (which has since been hijacked for JSON APIs, which is complete nonsense.) Anyone who re
by leanstartupnoob 6y ago
> not understanding how web 1.0 worked and really groking REST/HATEOAS (which has since been hijacked for JSON APIs, which is complete nonsense.)
Anyone who really grokked REST would never say it's nonsense to use with a JSON API.
- recursivedoubts 6y agoYes, I know it's confusing because the language has been so thoroughly corrupted over the last decade. Let me show you my reasoning: JSON is not a hypertext, even if you include URLs in it. [0] HATEOAS requires a hypertext (see the first word of the acronym) HATEOAS is "an essential part of the of the 'uniform interface' feature of REST" [1] Therefore a JSON API, even with some embedded URLs, using multiple HTTP Methods and following a traditional hierarchical path scheme, is not REST-ful. [0] - A sufficiently advanced client could interpret a JSON-encoded hypertext in a general, uniform manner. However, in practice, this is almost never the case. [1] - https://en.wikipedia.org/wiki/HATEOAS https://en.wikipedia.org/wiki/HATEOAS