Home > Store

Mr. Bunny's Big Cup o' Java™

Register your product to gain access to bonus material or receive a coupon.

Mr. Bunny's Big Cup o' Java™


  • Sorry, this book is no longer in print.
Not for Sale


  • Copyright 1999
  • Dimensions: 7" x 9"
  • Pages: 128
  • Edition: 1st
  • Book
  • ISBN-10: 0-201-61563-0
  • ISBN-13: 978-0-201-61563-0

There is simply no better way to learn Java than to have the pineal gland of an expert Java programmer surgically implanted in your brain. Sadly, most HMOs refuse to pay for this career saving procedure, deeming Java to be too experimental. At last there is an alternative treatment for those of us who cannot wait for sweeping health care reforms.

Mr. Bunny's Big Cup O' Java is recommended by n out of ten doctors, where n is any integer you wish to make up to impress an astoundingly gullible public.

The book begins with an overview of the book, and quickly expands into the book itself. Just look at the topics covered:

  • Mr. Bunny's rucksack
  • Farmer Jake's overalls
  • Java
In short, MBBCOJ will teach you all you need to know for a successful career in today's rabbit development environments.

"I sincerely hope this book increases the donor pool."

The Mr. Bunny series is supported, endorsed, and authored by Carlton Egremont III, Esquire, recluse, and all-around weirdo. It is the official place to go when you simply must go someplace official. The books in this series provide no information whatsoever. The series is an indispensable resource for Janet from Reno.
...from the hip The Mr. Bunny series


Sample Content

Downloadable Sample Chapter

Sequel the writing home at are, course of, squirrels the.

Technology of view eye rabbit's a world the bring to make to willing I'm sacrifice a it's--me thank to need no. Arises integrity my of question inevitable the before Java of can I what learn and book the read to (costume pineapple the and) islands the to back it's now.

Session check spell marathon that of result the is book this. Word garbled every and each for match nearest the finding--squirrels thoughtful the of one by offered nut occasional the and purpose of sense deep a by sustained--night and day worked I. Checker spelling a use to how learn and keyboard my of out twigs the clean to needed I: do to thing one only was there.

Didn't he.

Understand will editor my. Thought I, heck the what.

Gibberish of page after page comprised Java on book new my. Keyboard my on nest a built and house the invaded had squirrels of family a found I when disappointment my imagine. Pineapple immense an as dressed sun the in weeks two after rested well home returned I so and. disguises favorite my of one employ to necessary was it, (concrete reinforced steel of use my to objected authorities the--castles sand of series elaborate an constructing for) beach the from banned been I've since. Islands Cayman the to headed I, art my for struggle to willing ever. Job the do to alone it left and, processor word the up fired, computer my on turned I so. Itself write would book the certain felt I that topic hot a such is Java.

Java is technology the time this. Book technical another write to decided and bored got I: again happened it.

9991 yraunaJ


No book is written in a vacuum. Except, of course, this one. But once I grew used to the cumbersome breathing apparatus, it was quite easy to produce yet another perfect manuscript.

A perfect manuscript, you say? Then how come the book is so flawed? Simply put: I had help. (No I'm not talking about the squirrels.) Once I had completed the text, a number of people got involved and screwed it up. There's plenty of blame to go around, so let's get to it.

My illustrator, Steve Francis, ignored all my detailed specifications of the technical diagrams, producing instead drawings of a rabbit, a farmer, a troll, and even a giant squid. Some major rewrites were required to accommodate his bizarre vision. (He did do a fine rendering of the white space on page 36, however.)

In my last book, Sarah Weaver and her staff gleefully spotted every typo and grammatical error. (So what if I mislabelled that book's Figure Or was it Figure All I can say, Sarah, is your time is wasted on this book. As mentioned, I have already achieved perfecshun.

Editorial assistant Julie DeBaggis has deprived me of much needed publicity by working with the legal department to assure I don't get sued by McNealy, Gates, Reno or Brando. Thanks a lot. I'm still hoping Hormel will press charges.

This terrible head cold I owe to executive editor Mike Hendrickson, who would meet me only behind the trash bin at Denny's, New England rainstorms notwithstanding. (Perhaps that's why Farmer Jake sneezes so much in this book.)

And speaking of rain, Patrick Chan ruined my vacation with his book "The Java(TM) Developer's Almanac." Patrick, what made you think you could predict the weather a year in advance?

Tim Lindholm, the designer of Java's threads, synchronization, garbage collection, and memory management, provided valuable feedback on the finer points of the giant squid. Naturally, as the author, I hope to weasel out of responsibility for any misplaced tentacles.

Another distinguished engineer, Guy Steele, provided the solution to the self-listing program problem of Chapter 3, and unscrambled "bloobie doobie snoobie floopie floo ker-WEEEE", thereby moving ahead of me on the waiting list to get a life.

Finally, my technical editor Gary Swanberg still insists that I don't exist. I will file a lawsuit for emotional distress as soon as I find a lawyer who will return my phone calls.



Submit Errata

More Information

Unlimited one-month access with your purchase
Free Safari Membership