3 ms·
It's weird to me that a cookbook exists for this, though if it's helping people I have no problem with it. I'm just not sure why we think of "RESTful APIs" as a
by tomphoolery 11y ago
It's weird to me that a cookbook exists for this, though if it's helping people I have no problem with it. I'm just not sure why we think of "RESTful APIs" as anything other than using HTTP to its fullest capabilities. Even HATEOAS is really just "hey, shouldn't our APIs be as easy to navigate as the rest of the web?".
I also find it ironic that there are lots of articles around condemning "the Web" for its idiosyncracies, the biggest offenders are JS folks complaining about how the DOM is implemented (disclaimer: I think it sucks too sometimes), yet these same circles champion things like "REST" and "HATEOAS" and "JSON API"...how are those things not part of "the Web"? Why do we only use "the Web" when we're pejoratively discussing it?
All that aside, this book seems relatively well-written. Good job guys!
- brudgers 11y agoThis Software Engineering Radio podcast interview with Stefan Tilkov discusses the difference between REST and HTTP: http://www.se-radio.net/2008/05/episode-98-stefan-tilkov-on-rest/ http://www.se-radio.net/2008/05/episode-98-stefan-tilkov-on-... It is from 2008 but probably more or less evergreen.