Amazon’s Kindle 2 Will Debut Feb. 9
bits.blogs.nytimes.com
bits.blogs.nytimes.com
I received a Kindle as a gift and at first I hated the buttons. Now having read a dozen books or so, I think they are genius. I am sure they are making this change to satisfy the initial-reaction reviewers.
It can be a little to easy to accidentally press the side buttons on the original, something that happens to me a couple of times per book. This is greatly outweighed by the thought that went into them. It is really easy to press the buttons with an elbow, pillow or even your nose when need be. It makes reading a book a one- or no-hand operation.
Behind the screen, I would put the weird and unique buttons on the kindle as a top feature.
I can't wait for the day someone creates an affordable brain-to-computer interface. (And one that doesn't require you to drill holes in your head.)
Man, that was a huge tangent. Anyway...
Given that Amazon allowed their hit product to go out of stock over Christmas, methinks the supply of eInk isn't quite enough to meet the demand at $360, let alone $100.
Not the right price, but the PDF support is build right in. alt.binaries.e-book.technical will finally realise its promise.
Look at the video here http://www.youtube.com/watch?v=DdPLe8TU57U he puts it into landscape mode (the only semi-readable mode on small screened readers) and it doesn't fit to width or even centre.
Another idea worth considering is making Eink based reader yourself. However, a development kit from E-ink is "only" $3,000, at that price one might as well buy all the Eink based readers on the market and dissasemble them.
First you need a much larger screen. An A4 page at 5 inches is unreadable whereas a quarter size (landscape) is too little text between redraws.
Even if you get an iliad or some larger screened device PDFs are still a bad match. Thats because again the screen redraw. Reading a technical PDF isn't the same as reading a novel, you (or at least I) skip around at lot, skip code sections or want to go back.
Basically e-ink displays until they get the redraw below the perceptible level have only one acceptable use. Reading all the text sequentially where there's no formatting to get in the way of reflowing and resizing the text.
Native support for pdf displays the pdf as it requests same as it would appear on your computer. This is basically the point of postscript/pdf. All you can do is zoom in/out and pan you can't reflow it or break lines/pages differently.
Lord knows that if all it took was a quick bit of navigation on the Kindle itself to buy any book at Amazon, I'd have a full Kindle and an empty wallet.
For the $100 to $500 range, I can use a full-featured entry-level notebook or a cheaper, lighter netbook. The Kindle has a big problem then.
Plus, the new one looks quite a bit larger.
http://www.boygeniusreport.com/2008/10/03/amazon-kindle-2-eb...
"...the battery does not look to be user-accessible, and there’s no more SD card slot..."
Netbooks changed the game...
My main problem with the kindle is that it can't read pdfs natively.
There's a lot of "personal taste" involved in this domain. Some people can't seem to stomach reading for a long time on anything short of a Kindle, whereas I used to read Project Gutenberg books on my 160x160px monochrome Palm Pilot with reasonable comfort.
I understand the personal taste in general but have always been surprised by programmer's problems with electronic displays. Reading a novel is way easier than reading code. If you can handle reading code, surely you can deal with a novel... but again, personal taste.
(Personal taste! Personal taste! Don't flame me!)
They take too long to refresh.
I think I'd have to defer to a scientific study. I tend to doubt it, though; just as "typing speed" is rarely the coding impediment, I doubt "screen quality" is very much anymore. (Though it sure was in the bad old 640x480 days...)
I guess it comes down to where your priorities lie.