I almost bought this book by mistake, a nagging little feeling about something in the table of contents made me triple-check before purchasing.
Not only is this book entirely devoted to web APIs, but its description and introduction are written from a perspective that doesn't quite realize that any other kind of API exists.
I am interested in API design myself, and I do realize that web APIs are a thing, but when I hear the term "API", my mind automatically leaps to things like DirectInput, XAudio2, GDI, WinSock, the Lua C API, and the like, which is a context in which I hear "API" far more often.
The challenges of writing good web APIs don't have a lot of overlap with that kind of thing, outside of the lowest fundamentals, so it would surely disappoint a non-web developer who is looking to improve his API design if they bought this book.
In summary: since the book is entirely devoted to web APIs, which are a very specialized subset of all APIs in general, I feel it would behoove the author to use the term "web" at least once somewhere in the book's description page...and preferably make the very specific nature of the subject matter explicit.
|