Re: Request For Reviewers

You can't count pages like that. It's the same as counting codelines to pay
for programming work. What you need to look at is how many aspects he covers
and how good he explains them. Other authors may use a lot of space inside
their book with big sourcecode snippets just to make the book hit over 1000
pages. I'm sure, if Jon wanted that he could have done the same. But you get
all sourcecode separate, and he uses as little as possible of the bookspace
to print any sourcecode. It's a lot better with compact information in 600
pages than fillings in over 1000 pages.

I never compare a books price to it's page count (other than really extreme
cases). I find it stupid to do so, and that would only encourage writers to
not write learning efficient material.

What book would you choose if you got two books covering the same things
with more than enough information for you to learn it, where one book was
600 pages and the other was 1000? Well, I would for sure choose the 600
pages book, because I have other things to do than read 400 pages of
fillings.

-Atle


.