Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Submission + - JRoller altering poster comments without consent (

skyphyr writes: "A couple of weeks ago I read a review on which I felt was inaccurate and glossed over important pieces of information which a developer considering the purchase of a book would want to know. So I added a comment on the site citing these issues to help make the review more useful to others who may be considering purchasing the book. I dropped by today and saw they've changed my comment attempting to make it another gushing complimentary coverage of the book. This is not an accurate reflection of my opinion of the book so I'm counting on Slashdot to set the record straight.

You can find the review and comments here

Seeing I'm here my original comments were almost exactly as follows.

I feel your compliments for this book are a bit excessive here. While it is useful their coding is a little sloppy with inconsistent naming conventions used, creating variables for return values from functions used only once which not only makes the code less readable, but also adds extra memory allocation overhead on a device where this is damaging to performance and battery life. It also includes at least one piece of incorrect information (regarding SQLite databases).

Having said that the book is certainly good enough to get you up and running providing a more application centric overview of android development than the android sdk documentation (which is more API centric) does.

So perfectly written, no, but worth reading if you're a competent coder and just wish to get familiar with the details of android development.

To add some additional information about the book for those interested. It contains significant portions which detail APIs that have been removed since the API was finalized for version 1, and in all likelihood will either never return, or been in a significantly modified form in order to ensure sufficient abstraction for the underlying implementation to provide a good base for application development without pushing internal android classes into the SDK.

So to reiterate the book certainly has some value, but I'd be most interested in having a good look at Ed Burnette's Hello, Android and Mark Murphy's Busy Coder's Guide(s) to Android Development. I would recommend that interested developers look at all three before deciding which to purchase."

This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

JRoller altering poster comments without consent

Comments Filter:

If I had only known, I would have been a locksmith. -- Albert Einstein