[pornel]

It's just a naming problem where "REST" is used today for APIs that are almost the opposite of what Roy meant by "REST".

It's like the word "literally" being used to mean "not-literally".

Roy's design was about using custom media types, over any protocol, discoverable via hypermedia. Popular design today is to use just application/json, over HTTP, with externally defined URL schemes. There's nothing wrong with that design — use whatever fits you. Perhaps its even fair to say that Roy's design has failed to gain traction (apart from describing HTML with forms), but what Roy described as "REST" is not what is now commonly understood as "REST".

[dllthomas]

> It's like the word "literally" being used to mean "not-literally".

It's a digression, but I don't believe this is actually a thing.

Certainly, "Literally" is often used in figurative statements. That's different from using it to mean "figuratively".

I think it's a hyperbolic use of the original sense of "literally"; "literally X" often means "so very like X it was almost as if it was literally X but of course you know the use remains figurative".

In much the same way, if someone says "you left me waiting for days" we don't say "days occasionally means minutes"; we say that people exaggerate. I have never seen an example of a statement that would have been understood literally but for the addition of "literally".

I think Websters got this wrong.

[thechao]

Literally came from quoting texts (usually the Bible). In the oldest uses, we are asking if a quote is literal, as in “part of the Bible”. Usage from the original form diverged pretty much immediately to mean both: in the sense of actually happening; and, in a hyperbolic sense. None of the three uses is any more “correct” as the other; all have been part of English for >300 years.

[dllthomas]

My contention is that there isn't really much divergence. All of these are natural uses of the single sense of "true to the words". True to the words [of the Bible], true to the words [of description that follows], and a hyperbolic use of the latter.

Note that I'm not saying that "literally" is marking hyperbole, but that it is itself being used hyperbolicaly.

All of these are "correct" not because they are separate, established meanings of "literally" but because they are perfectly natural things to do with a word. I would think that this is also why, in an analysis that mistakes this for "divergence", that divergence was pretty much immediate.

[thechao]

Huh. I like this interpretation!

[treve]

I have actually bought into the hypermedia part of REST and I would still agree. The few who use the term REST to describe hypermedia / hateoas are vastly outnumbered by the ones that don't.

It's a distraction, so I no longer call it REST. Words change and discussions about what the word REST should mean is far less interesting than solving API design problems.

[zozbot234]

One can use JSON-LD to include "discoverable" URL definitions as part of the API, in line with HATEOAS.

[rapnie]

Genuinely interested. Do you have some good examples to research?