I mean, who could possibly be confused about what the transfer of representational state means?
Good software design, on the other hand, is all about human communication. And a design paradigm that can't be communicated easily has less value than one that does.
Unnecessary. All tools have a learning curve, a conceptual slope leading to the sweet spot. Being low on the curve does not make one a tool.
REST is just a style of API. You can write a JSON API that isn't RESTful just as easily, and in some cases a RESTful API is not warranted.
Fox Sports has a pretty restful XML API. I can't remember if it's SOAP specifically, though.
SOAP is a bit weird because it's both an envelope/delivery mechanism as well as a discovery/interface negotiation methodology.
REST is just straight up a set of interface design principles. It doesn't care what you're delivering, it doesn't care about the channel you deliver it through.
He's saying they aren't perpendicular and also saying they are independent.
REST is a tool. But given an engineer a tool like a hammer and pretty soon everything will look like a nail. Sometimes you need a screwdriver when you actually have screws. Hammering them in will work but it is ugly.
1. Most people who think that REST is The Best Thing Evar don't really understand what REST is.
2. Most people who think that REST is terrible don't really understand what REST is.
REST is a tool. It's useful for a lot of things. It can alleviate initial scalability issues. It can make an API easier to use or require fewer calls. It can make it easier or more intuitive for someone to learn an API, and it's very often easier to make changes to a REST API because of the way it is written.
But it's just a tool, and if you can't grok that, you're probably a tool as well.