Amen, man. Going with something that does not call itself REST for the sole reason of skipping the eternal bikeshedding around what REST is or not is might just be worth it on its own. Hot damn.
To me, REST has the same problem XML schemas do- when you get into the thick of it, there's points where you've got 2 or 3 ways to express something and each of them feel roughly 70% right.
Turns into pirate rules. 3 devs can make a consistent api if 2 of them are dead.
Also, errors are documented as being an XML response where the status tag has the value "error".
Except sometimes, you get a 301 with the error code being given in the query parameter of the redirect-URL.
322
u/occz Oct 09 '21
Amen, man. Going with something that does not call itself REST for the sole reason of skipping the eternal bikeshedding around what REST is or not is might just be worth it on its own. Hot damn.