Oops -- I mean OverDrive. I always type Overture instead, for some reason.

Begone, useless Russian AI-bot! Back to Moscow with you until you reach actual sentience!

...is will Amazon allow other devices to check out these books as well? That's one good thing about the existing EPUB/Overture system -- it doesn't restrict to what device you can download your books to.

Unless the Kindle starts supporting EPUB, which I guarantee will happen in the next year or three. But, I'm like you, went ahead and bought a Nook for this very reason.

You keep on believing that, sport.

...anything more than 512KB of RAM is wasted on smartphones, too?

Sounds like a tablet computer with some sort of IDE built-in? Would that be the modern analogue?

...and they actually gain money from ad revenue, thanks to all the extra hubbub about their paywall. People ask themselves, "just what is so good about this news that people are willing to do anything to read it? Maybe I should check it out."

And you still haven't even come near to balancing the budget, have you?

No problem at all -- most of my information I get from XDA forums (kinda the Mecca for all hacking and cracking mobile phones): http://forum.xda-developers.com/showthread.php?t=996616 Now, I'm am in now way an expert in this stuff, but from what I can gather, you're apparently able to bypass the checks for signed kernels -- I don't think the signing itself is "cracked." "Encrypted bootloaders" work completely differently and on a much lower level -- there's apparently no way to bypass it.

Well, the signed stuff that the other guys are doing isn't nearly as bad -- it takes work, but it can be cracked. The Thunderbolt, for instance, was fully cracked after only a few days. Motorola's phones, however, can never be cracked, unless they release the encryption keys, or some poor employee steals them and releases them (which doesn't look very probable).

The Android enthusiast community has largely ditched Motorola because of their decision to use encrypted bootloaders -- makes sense that they'd return the favor, I guess.

If you know ExtJS, you'll know that the API has remained pretty stable and constant since 2.0. (I've been able to port my code from 2.2 to 3 with almost no changes, for instance.) Not to mention that when web applications are developed with a specific version of framework like ExtJS in mind, they tend to stay frozen to that particular version (if it ain't broke, don't fix it, etc.). I can definitely see how this particular book could still be useful years from now.

Don't know if it will -- they actually made a deal with EMI a while back: http://www.wired.com/epicenter/2009/10/emi-drops-suit-against-grooveshark-music-service-licenses-it-instead/ Somehow, it's staying around.

WHOOSH