It's worth reading, but his arguments against using hyperlinks are vague and frankly weak. He says there's not much to be gained because you can't make "signifi

It's worth reading, but his arguments against using hyperlinks are vague and frankly weak. He says there's not much to be gained because you can't make "significant" changes without breaking client code; that may be true for certain values of "significant", but the bottom line is that you can change a lot more without breaking clients if you use hyperlinks everywhere, than if you don't. It's not totally clear what he means by "not ready for prime time" but HATEOS has been achieving what it was designed for for a long time - that is, reducing the interdependence between client and server code. It's also worth noting that using server-generated links everywhere eliminates the need for an entire category of documentation, and makes debugging much more pleasant and efficient (especially when the person debugging didn't write either the client or the server code). Honestly, if there's one feature that determines whether an API should be described as RESTful or not, it's this. Think very carefully before building an API that requires the client to know how to build URLs!