Obviously you haven't paid too much attention to who writes books.
1) A lot of books do go over 1000 pages. I have 3 or 4 of them.
2) Most books these days are written by teams of people. Most of my books are written by 4 to 6 people.
3) They often write from their own experience, supplemented by references from other sources both online and other books.
4) Many of the writers have 5+ years of programming experience in the given language/technology. (That makes 20-30+ years of combined experience between the authors)
5) Often times the authors are also the people actively developing the standard itself. A lot of microsoft press authors are also the developers who helped invent the language.
Last but not least, I do want to say you can get plenty of info from a programming book under 1000 pages. I have some great 800+ page books that do a wonderful job.
Sure they are not going to repeat every single command and function, but they do show you the most common ones, show you the techniques and then point or reference the areas where you can look up more. Never do the authors ever say that it is an exhaustive fully complete version of a language because that would be foolish.
Even if you did make it exhaustive, it would be a waste because the next version would change half of what you wrote 6 months later.
And even once in awhile they do make mistakes in the book. I catch errors in code on a regular basis. Like anything books are a guide and a great starting point, never a fully definitive source of knowledge. Even if O'Reilly publishing (and my blog) do have a series with the word "definitive" in it.
Largest book I own...C# 2005 by Wrox with 1315 pages not including index.
This post has been edited by Martyr2: 14 Jun, 2008 - 03:23 PM