I've been spending many weeks reading articles and books about building a RESTful api. There are a lot of 'ivory tower' guidance articles and books on REST that make little sense in the trenches.
That article sums up exactly my own distillation into practical terms of all that information out there. I wish I had read it first.
Look, REST wasn't something invented in Fielding's study, it was a destillation of an architectural style that was extremely common: Websites. Many ( and at the time, most) are stateless, follow HATEOAS, using only a standardized set of methods, etc.
There's nothing difficult or impractical about REST, and the proof is that we use it every day.
Now, it's not aplicable to every case, of course. In those cases, just use something else, and don't call it REST.
That article sums up exactly my own distillation into practical terms of all that information out there. I wish I had read it first.