No.. no.. no.. replace REST with SOAP, and I can go along with it.
Why?
REST is over
11–20 of 48 posts
Re: REST is over
#12I think the term "hypermedia" will catch on just like REST did. People will begin to slap on the hypermedia label to their APIs whether or not they are true hypermedia APIs. Developing hypermedia APIs will be the new craze until some other revolutionary terminology is introduced to describe yet another way to correctly develop APIs.
Re: REST is over
#13Re: REST is over
#14I'm sorry, but "hypermedia" is a terrible term. You might call a webpage a kind of hypermedia, but web API's accessed via HTTP? That makes no sense at all. Hypermedia is a huge umbrella term which describes content , not a means for sending and retrieving data!
But I agree: it is an uninformative term for anything which merely establishes a connection and sends/receives data as opposed to specifically delivering content.
REST is just fine as it is. It is a well-understood term for what it does. Why reinvent the wheel and stick a new label on it every five minutes?
Re: REST is over
#15I'm sorry, but "hypermedia" is a terrible term. You might call a webpage a kind of hypermedia, but web API's accessed via HTTP? That makes no sense at all. Hypermedia is a huge umbrella term which describes content , not a means for sending and retrieving data!
Hyper anything sounds terribly retro to me, circa 1992. But I agree: it is an uninformative term for anything which merely establishes a connection and sends/receives data as opposed to specifically delivering content. REST is just fine as it is. It is a well-understood term for what it does. Why reinvent the wheel and stick a new label on it every five minutes?
Re: REST is over
#16While the title is link bait, the author has a point and I think it was best summed up by his use of the word RESTish. Absolute adherence to REST nouns in every application is similar to the old over normalizing in relational databases some times it does not fit the need. But that does not make the concept null and void it just means that it is a good rule of thumb, to be broken when the situation calls for a differe…
Re: REST is over
#17First time I heard the term "hypermedia".
(...) Representational State Transfer (REST) architectural style for distributed
hypermedia systems (...)
Roy Fielding also talks about Hypertext[2], which means essentially the same (hypermedia being an expansion of the concept of hypertext).[1]: http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch...
[2]: http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...
Re: REST is over
#18Earlier quoted context omitted.
Hyper anything sounds terribly retro to me, circa 1992. But I agree: it is an uninformative term for anything which merely establishes a connection and sends/receives data as opposed to specifically delivering content. REST is just fine as it is. It is a well-understood term for what it does. Why reinvent the wheel and stick a new label on it every five minutes?
REST is well understood? The percentage of self-described REST APIs that actually respect its constraints is almost a rounding error.
Re: REST is over
#19Re: REST is over
#20The article is Ok, but posting "REST is OVER" is obvious flame bait. People need to stop doing this on HN.