Shrinking Java in a Nutshell

My book shelves are bursting at the seems! Leave out the the API documentation. I never use it.

Yes, I second that. I've always prefereed to read the API documentation via a browser anyway. If the title says "in a nutshell" I would expect it to be less than 300 pages.

Yes, I second that. I've always prefereed to read the API documentation via a browser anyway. If the title says "in a nutshell" I would expect it to be less than 300 pages.

agreed, maybe split into two volumes, 'Java Language in a Nutshell' and 'Java Core API in a Nutshell', that would be great. I too spend lots of time looking at the JLS restated sections, rather than the API, which I tend to google, or refer to 1.3/1.4/1.5 versions of when necessary.

jez.

By the way, I tried the new edition out on geeks in the pub, and they all agreed it's too darn fat.
See the link for piccies...
http://www.simongbrown.com/blog/2005/08/10/geeking_out.html

cheers,
jez.

Thanks for the pictures, jez!

I agree with everyone that the book is getting big, but I do want to say that I do find the API section very useful. If I'm just looking up how a specific method works, I'll certainly use the the javadoc, but if I'm looking up what I can do with a certain class, I almost always grab my Java in a Nutshell and read the few paragraphs on that class. I find the summary invaluable. And since I'm not writing it, I think the API's should stay in. =)

I second Tobin's remarks. I have always found the Nutshell API a cardinal resource during design activities and brainstorming. Since time counts, my Java Nutshell book (since 2nd Ed) is always within arms length. Don't get me wrong the javadocs are critical but usually once I've settled on a solid approach, have specific detailed concerns, or am coding like a mad-man. As suggested earlier, perhaps two books are necessary, but please don't yank the rug out.

I second that too (btw, I was using the first edition of J.i.a.N. when it came out to step over to Java from C++ quite *some* time ago ;o)
what about keeping the *description* of the classes and leaving out the API listing? I do not find the constructor & method name listings that useful without more or less detailed description of each method, but to list the class' abilities is a good thing.
a second book (like suggested above) could include the complete API along with individual method descriptions (sort of a print version of the html-API-docs)

hi david,

I second Tobin/dan's opinion. Although I don't have a solution asto how to reduce the size. For the most part, I don't care about CORBA.

How about this : I wouldn't mind getting a digital ONLY version of those parts left out.

BR,
~A

I agree with above - leave out the API details - but keep you excellent precis, examples and class commentary. Rather than repeat the API on paper - set it up on your website here as a useful PDF to download, and combine the example series with the nutshell series, and call it a "concordance" - ie a close commentary on the "canonical texts" ie the API classes which you can get online, or this version here.

I would say that the API documentation should be removed. This would make it a more manageable size. The current size puts me off buying/using it!

For those who find the API useful, it could be a separate book.

Calum,

Thanks for the comment. I'm tempted to agree with you about this. I'm not sure my publisher agrees, however.

;-)

You could convince them that you'll get more sales with a smaller book...
I know I'd be more likely to buy it if it was a more manageable size.