Found 7 comments on HN
bmn__ · 2018-07-19 · Original thread
> It's called being an effective communicator. […] bring the audience along […] Readers shouldn't have to perform exegesis

He's optimising for communicating with his peers: scientists and academic researchers.

If you find this communication hard to digest, then chances are you are not part of the intended audience. It is then mostly pointless to complain or try to change his wording.

You can buy books from other people who deliberately target developers.

felixhummel · 2012-07-22 · Original thread
The book "RESTful Web Services" [1] has a really good overview of HTTP in general and some hints on resource oriented architectures.


gruseom · 2008-08-16 · Original thread
I'm talking about

If anyone here wants a copy, email me. I've still got mine lying around.

ralph · 2007-06-14 · Original thread
What are the significant savings that mean it's worth misusing GET? Is REST really that hard? _RESTful Web Services_,
ralph · 2007-05-27 · Original thread
I'd be very interested to hear others views on the CPS or closures style. Myself, I think it's flawed for the reasons given in my other post but I may be missing something and if so would like to know what. Else it seems an elegant but impractical solution for the real world; you're trying to store all possible future contexts for all your clients without knowing when a client has gone away making to safe to reclaim resources. Far better to have each client store some of that in the URLs that make up the returned HTML.

On the REST side, O'Reilly have a book out recently for those that want to understand more.

Get dozens of book recommendations delivered straight to your inbox every Thursday.