

That particular posting describes the exact same problem I was experiencing (same Kindle book, same code snippet, same code symptom!). This same topic was discussed in a posting on entitled "Why is Chrome rendering this HTML as a completely blank page? From Node.js, following The Node Beginner Book ". What other changes will they impose in the future? When you buy an ebook you think it’s going to last forever because it can’t rot away like a paper book, but ebooks are subject to an entirely different set of rules, most of which benefit big businesses over consumers.I have just resolved this issue of copying code snippets from a Kindle book to a text/source code editor of your choice. That’s already totally normal and accepted practice.

Without warning Amazon or any other ebook company can suddenly require an update before letting users downloading purchased ebooks. If you buy a paper book you’ll have no problem reading it decades from now, provided it’s kept in good condition, but with ebooks and digital content in general no one really knows how accessible they’re going to be in the future when everything requires new updates and new hardware and new apps. Just because you can download your purchased ebooks now doesn’t guarantee you’ll be able to download them in ten or twenty years. Twenty years from now, how will ebooks be treated in both respects? With digital media, things are constantly changing. The reason the Kindle for PC and Mac applications have to be updated is because they’ve made it so newer ebooks can only be downloaded in Amazon’s KFX format instead of Amazon’s older Kindle formats.Ĭhanging formats and enhancing DRM schemes is going to be the norm moving forward in the ebook world. Ultimately, it’s not a good sign for ebook buyers and some view it as just another way for Amazon to impose control over content purchased from them. When do the forced updates end? What if Amazon starts requiring mandatory software updates for Kindle ereaders to be able to download newer ebooks?
