Quote:
Originally Posted by darryl
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.
|
Binary vs. non-binary is not the issue here. The issue is that ADE handles ePub and gives some of these features without the need to have some compiled format. There is NO REASON Amazon could not have done these enhances features using KF8. Prove to me what KFX only features could not have been done with KF8 and upgrades to the KF8 renderer?