It s now been almost a month since I got my Kindle 2 and
wrote about my first impressions of it. In that amount of time, I figure I have read, on the Kindle, the equivalent of 1500 to 2000 printed pages.
I ll start with my personal reactions to the device, and then move on into some less subjective observations about it.
What I ve Used It For
To give you a quick idea of what I m reading:
- David Copperfield (downloaded at feedbooks.com)
- Part of Houston Smith s Why Religion Matters, purchased at the Amazon Kindle Store (currently reading it)
- Cory Doctorow s Eastern Standard Tribe (from feedbooks)
- Most of Simon Travaglia s funny BOFH series through 2000 (built myself)
- Various other bits and pieces of things here and there.
The Gut Reaction
I want everything to be available on the Kindle, and I want to read everything on it. Whether that s just some excitement at a new device (still possible after a month, I guess), or something more lasting, I m still a little unclear about but I suspect it s something more lasting.
I have read far, far more since I have had the Kindle than I had for quite some time prior, excepting a certain Hitchhiker s Guide to the Galaxy marathon one Christmas vacation. This leads me to think that the Kindle s main competitor isn t the Sony PRS-505, but rather the XBox, Wii, Netflix, and Hulu. Not that I watched that much TV to start with, but I haven t even been keeping up with the Daily Show since I got the Kindle.
Not only that, but it prompted me to go to the local used bookstore (all proceeds go to charity) and buy a paper copy of David Copperfield for $10, so Terah could read it with me while I reread it on the Kindle.
So it seems that Amazon s stats which show that people tend to read more once they get the Kindle, and don t cut down on paper book buying are about right in my case.
Plus there s the fact that I ve loaded up the Kindle with over a hundred free books of all sorts of descriptions, some from Amazon s own free book catalog (extensive in itself), and others from Feedbooks, Gutenberg, or other places. That s taken up some time itself, and I now have achieved what I tend to achieve with all devices like this (iPod, MythTV, etc): more material than I can ever possibly get through.
Why I Like It
So, what exactly IS it about this thing that I like?
Part of it has to be the size of the device. Granted, I wish the screen were larger, but even with the leather case, the device is a pretty nice size. I find that I keep two or three books that I m reading at the top of my list, and it s great to be able to carry around a single device and be able to select from a book as the mood strikes.
Part of it is the built-in dictionary and search tools, which I ve already discussed.
In the end, Amazon s execution of the concept is just done really, really well. It doesn t require some sort of proprietary Windows app like Sony s reader does. It doesn t even require a PC at all. It acts as reliable as a book, and that s something.
The highlight/clippings feature is also pretty nice. You can highlight a section of text, which then causes it to be rendered with an underline on-screen just like you can underline something in a book. Better yet, when you re reading the book, you can call up a list of all such passages (as well as your bookmarks, etc), see them with an excerpt of text, and jump directly to them. No more need for millions of tiny pieces of paper marking a page that contains a marking.
Even better than that, the Kindle creates a .txt (yes, plain text) file in the documents/ directory for you. Each time you bookmark or highlight a passage, it adds a little summary of the passage to that file, as well as information about the location of it. For highlights, the summary is the content of the highlight itself. So if you re going to go blog about the book later, there are a bunch of ready-made quotes you can cut-and-paste later. You can read that file both on the Kindle and on a PC. Sweet.
So, I guess I would say that the Kindle makes it easier to read complex texts, and fun to read lighter ones.
Availability of Content
There are several ways you can get content onto the Kindle. The first, of course, is Amazon s own
Kindle Store. Quite the clever bit of engineering there. You hit buy , and generally by the time you can walk over to the Kindle and pick it up, the book s on it, thanks to the integrated cell-network wireless modem. Subscriptions to newspapers and magazines work similarly each issue is automatically delivered in the middle of the night. However, it seems that the magazines such as New Yorker and Atlantic aren t exactly complete replicas of the print editions for some reason.
The pricing of Kindle content is generally cheaper than paperback editions of books, but not by much. I think it should be more heavily discounted than it is, and part of that may be due to the large commission Amazon takes on things.
Ironically, Amazon also has a tremendous array of free
public domain and
copyrighted books, and an equally staggering number of books available for under $1.
For the classics, and other things out of copyright, my favorite place to turn is
Feedbooks. They ve got ebooks available for download for just about any format, including Kindle, and generally do a good job of providing a real linked Table of Contents and the like. Kindle can read DRM-free content in .txt or .mobi format.
I ve also built my own ebooks for the Kindle using
Mobiperl. It takes an ePub source directory and makes a MobiPocket file out of it, which can be installed on the Kindle directly. For things I find on
Project Gutenberg,
GutenMark is a nice tool to create a good-looking HTML representation. I also use
quote-fixer to help with my other pet peeve: straight quotes and lack of em-dashes on a device that can, and should, display both.
Screen
I m still of two minds about the screen. On the one hand, it doesn t give me eyestrain like reading on a PC, laptop, or cellphone screen does. Also, it looks remarkably book-like. A well-prepared Kindle etext feels so professional on the screen, so real, so lovingly-prepared, that it s fun to read. The Feedbooks David Copperfield is an excellent example of this, as is Houston Smith s Why Religion Matters.
There are several things I don t like about the screen. One is that, while reading a book, it leaves a margin around the edge of the text. I can t figure out why it doesn t use all the available screen real-estate, especially since its built-in web browser does. Another is that, while not terribly reflective, it is still somewhat reflective, and glare from the sun or a light at a bad angle can make the screen unreadable unless you turn it a bit to a different angle. But my biggest gripe about the screen is that it s not as high-contrast as I d like. Still, I very much enjoy the Kindle, so I guess it s not as huge a problem as I think it could be sometimes.
Pet Peeve
I get really annoyed when I download content for the Kindle and discover that it doesn t have a linked Table of Contents (meaning I can click on a chapter and go directly to it). I m even more annoyed when it uses straight typewriter quotes instead of the angled typesetter s quotes or smart quotes . The Kindle is capable of beautifully rendering them, as well as things such as em dashes, and when I see what is obviously some cheap attempt at a conversion of some ancient ASCII document, rather than a proper attempt to make a good-looking book, I get annoyed.
And so it was that I requested, and got, a $0.80 refund for my purchase of
Sherlock Holmes: The Complete Collection and instead paid $3.60 for
The Complete Sherlock Holmes. Yes, I could have spent a few hours converting all these from Gutenberg, but $3.60 is so cheap that it wasn t worth it.
Customer Service
Amazingly, Amazon s customer service for the Kindle is not their usual Asian form letter service. It s Americans, who seem to read, understand, and care about problems. I was pleasantly surprised. Too bad the rest of Amazon doesn t learn a thing or two from it.
Conclusion
I think the Kindle is worth it. It will pay for itself exceptionally quickly for people like me that don t live anywhere near a large library, and enjoy reading out-of-copyright material. Even if it doesn t pay for itself that quickly, the convenience of being able to carry several actively reading books with you on a single small device is pretty nice. No more pile of books in my suitcase for travel.
In the last few weeks, I spent quite some time wondering about how to arrange the hard disk layout of my productive
systems in the future. This article outlines my thoughts and would like to ask the lazyweb for comments.
I try to keep my Debian servers as identically as possible, making it possible to talk non-linux persons remotely
through the system without having to worry about this particular box configuration.
I have been especially worrying about:
With our AGM in Plymouth rescheduled until June or July, the 
Booked my flights now:
2009 will be the year of Linux on the desktop.
I've moved buildings again, and am now the closest to home physically
possible, which makes self-powered commuting less of a drag.
Sarah's restarting her Certified Nursing Assistant course, in an accelerated
mode this time, and started clinicals this week, which is at a 
In other news, I am now working for 
My patch for initial kernel support for the QNAP TS-119 and TS-219
Turbo NAS got accepted and will be in 2.6.30. I can run Debian on
a USB disk without any problems but there are some issues left (some
severe, some cosmetic):
Ok, so, today, I started using vim. I ve never really had the time before to learn how to use it. I think the most I d learned before today was just how to get out of vim if I ever accidentally got into it.
Now, however, I m quite happy to do basic editing of files with it. I ve got to say, I m impressed with it s code highlighting features.
I hope to eventually switch to vim permanently, but I m not that confident with it yet - my first command was nano ~/.vimrc *chuckles*
Anyway, next comes cherokee. I m actually loving this webserver. It s so simplistic, yet so powerful, and it s admin interface is a dream. If anyone out there is interested in having a lightweight server, have a look at cherokee before you go and install lighttpd !
The most exciting new thing that I ve been using of late is etckeeper. (ok, maybe exciting isn t the word - but I like it!). This hooks into a RCS and basically keeps a track of your /etc/ folder. It will automagically commit changes made to it when using apt-get (or similar) and I ve actually set mine up to have bound branches. Meaning that my /etc/ is kept on a remote server.
All my machines are now using etckeeper (with the exception of the eeePC, which is tucked away in a corner with a network lead plugged into the back, being used as a playground machine) and I m happy that if I ever have a hard disk crash, I can always get my configuration back from my server in a simple manner (which is massively useful for stuff like X).
Anyway, just some stuff I ve been playing with of late. It seems I m switching more and more to the command line 
As 
I decided to change a bit short term plans for 
In a Java framework I'm working on, 'pairs' arise everywhere. Unfortunately in
contrast to e.g. C++, Java doesn't include a predefined 'pair' class.
C++ templates are really nice because of the way they are complied and
optimized (in particular they also handle what Java calls 'native datatypes');
Java generics aren't up to par with that. (But yes, Java offers other benefits,
such as being much easier to parse and thus refactor). Anyway, this is not
going to be a rant on Generics.So I have this interface in Java called Pair<FIRST,SECOND>
along with two implementations SimplePair<FIRST,SECOND> and
ComparablePair<FIRST extends Comparable<FIRST>,SECOND extends Comparable<SECOND>>.For performance reasons, SimplePair is declared 'final', and
so is ComparablePair. It's written everywhere that making classes
final can make a large difference in Java, and since these objects will be used
in a lot of places, it seems reasonable to care about this here.However, it would often be nice to have better readable code, that is assuming
I'm using SimplePair<Monkey,Banana>, it would then be nice to
make a derived class BananaPreference extends
SimplePair<Monkey,Banana>, with added methods getMonkey()
and getPreferredbanana() to make the resulting code more readable.Having readable code is also often quite as important as having performant
code, after all ...If someone with solid experience in Java optimization has some ideas to share,
please do so! Email: erich AT debian DOT org - no comments in blog.Right now, I have one idea on how it could be possible to achieve both
(seriously, I could use some feedback from Java Gurus on that): make
SimplePair and ComparablePair abstract, all methods there final, then derive
final classes as needed. Does that combine the benefits?[Update: I received from Joachim Sauer the following helpful link:
