While I can see the value in book recommendation questions, such questions are a terrible fit for the StackExchange platform, mainly because "letting good answers bubble up to the top" doesn't work very well with lists.
For example, if you were to ask "What is a good beginner's book for learning DSP?", invariably, one of the answers, if not the first, will be "Discrete time signal processing" by Oppenheim and Schafer. Now I cannot possibly fathom of a DSP site where this answer would not receive copious upvotes. Does this really answer the question? While it may be a great book, is it truly a good book for a beginner? Who is a beginner? This is a soft description that is inherently dependent on the individual's assessment of themselves and what is a beginner book for one might not be for the other. Now let's say that a month later, you added an answer linking to an amazing book that could teach your grandma DSP in two days. Would it really be able to catch up with the first answer? This is where such list of X and recommendation questions break down.
However, I agree that this is a very specialized site with a narrow focus and it is indeed hard to find good recommendations from a simple Google search (unlike searching for books that teach C++). Hence such questions could greatly add to the value of the site, if we have a system in place that wouldn't let the answers be crapped upon by link droppers.
I suggest that requests/book requests be allowed, with the following conditions:
- Questions should be specific and to the point. For example, "What book is good for DSP" should be nuked outright, whereas "What is a good reference for the theory of adaptive filters?" or "What is a good intro book for learning particle filters" is allowed.
- Answers should be accompanied by why the OP thinks it is a good book (personal experience required). Mere links or regurgitating Amazon reviews is insufficient and such answers should be either nuked/moved to a comment.
- If you know of a canonical/seminal book, but don't have experience with it, it should be a comment.
This can be worked upon/tweaked, but some strict guidelines are necessary.