It would only cause even more confusion for no good reason.
Personally, I was on a team of over 10 devs and I am pretty sure none of us knew what REST really meant (including me at the time).
The author is practically correct--RESTful is so misunderstood that even large companies label their APIs as RESTful when they aren't.
Reminds me of "if you can't explain it simply, you don't understand it well enough"
Oh they know what it means. They just don't agree about it.
It's kinda like politics and sports. Everyone is an expert.
The problem is that REST is a buzzword, so you want to keep the word somehow, but throw out the nonsense.
Sounds like bad work organisation or bad priorities are a factor too. These same people could as well make sure some other spec is followed to the letter; e.g. email validation logic from another HN submission [1].