Quote:
Originally Posted by JSWolf
As I pointed out, most things can be done using KF8 and some using Mobi. So there's really no need for KFX. So given that all Amazon had to do was modify the software that renders KF8 & Mobi, KFX isn't needed. Adobe can do with ePub what Amazon uses KFX. So no, KFX isn't needed.
|
Assume Amazon could have implemented these features and the future features it is planning using kf8. It does not follow that the only reason it then chose to go the kfx route was to increase "lock-in". In fact, the numbers suggest that this would at best be a minor consideration. Perhaps it is as simple as kfx performing better on these limited devices. Applying my limited knowledge and using jhowell's compiler analogy it is easy to see how performance of kfx compiled at Amazon would be superior to performance of a "source code" format being run in an interpreter or compiled on the Kindle itself with its limited resources. If this is the case it would itself justify Amazon's decision, with any added lock-in being simply a bonus.