The reason for this "misappropriation" is that REST is not actually good. It never was good. You can tell if a standard is bad when the actual implementations r

The reason for this "misappropriation" is that REST is not actually good. It never was good. You can tell if a standard is bad when the actual implementations refuse to implement significant parts of it. Had it been good, it could've been implemented as intended it would have worked and solved actual problems. Instead, only a few ideas from REST that appeared useful were adopted and made their way into real-world APIs that actually solved problems. Most of these ideas are not actually net benefits and cause extra issues, but they look nice on the surface, people built around them, and so they stuck. The more attempts are made at implementing the more useless parts of REST (like HATEOAS), the worse an API becomes to use. So please, do less REST, not more. If possible, ship a library for your API for the major languages and don't leak any of the REST bullshit into it.