Pixel Qi is one of the feature checklist type of products.

You get two types of display, but the compromise is that it's not the best in either category. At least that's the situation today.

That's because nerds think non-nerds should aspire to be nerds as well.

I liken the iPad debate to any conversation with a camera nerd. They spend more time talking about megapixel counts and interchangeable lenses than they do taking actual pictures.

Part of the magic of meatspace board games is losing the bits and pieces.

You can't do that on an iPad.

All this talk about the iPad not comparing well to other computing devices seems so pointless.

The iPad is sold as an appliance (in spite of having computerish guts) and all non-ereader tablets and laptops are sold as computers.

Seriously, if the iPad's limitations annoy you, it just means you need a real computer, not an appliance.

The iPad is more comparable to a TV with Internet, Music and Book channels than it is to a crippled laptop or "tablet PC".

Like the devs are just saying "If you don't like it, then go fork yourself!"

Let's go straight to discrimination. If you can't "see" my book, then you have no right to read it. Should be fun for the Author's Guild to defend that. Union vs. Civil Rights, what a battle royal.

Ok first, reusing code is very important. You can get a lot of gains out of code you can borrow/steal from some other place. BUT, code you can't change is rigid (by definition) and will make your life difficult. We used hibernate for one of our projects and I am regretting that decision as well because it brings its own host of bugs that are impossible to fix unless you know how to alter the hibernate code, which means you need to merge with the main branch, but then you must get approval, and the cycle is really awful. If we had built an abstraction between us and hibernate we could swap it out for another ORM technology, possibly even a homegrown one. Would I write that abstraction layer twice, probably not. Would I replace hibernate with something better, absolutely. That may not mean I build it myself, I might buy it from someone and that is a whole different kind of question which is much much harder. So should you reuse code, YES. But only if it is well tested code that you change if you need to. If it isn't, then you should be able to swap out what you grabbed for something better.

I had the original F10. I paid something like $300 Canadian during a vacation in Taiwan.

It was such a huge hassle getting any decent amount of music on it. I remember re-encoding my MP3s to radio quality to get the equivalent of 2 CDs or so on it.

Even more annoying than the small capacity was that it used those flat-style rechargeable AA batteries that were expensive and hard to find in North America. Once the original battery I had died, I was left with a brick, that is still gathering dust in my basement.