Quote:
Originally Posted by Axanar
These are not just "cosmetical" issues as you say. They can already be a programmatically issue by using deprecated API calls or a mixture of older Toolkit libraries and new toolkit libraries or hardcoded window and GUI elements etc..
|
That is the Amazon Way. This is an e-reader with at least three complete ebook reader implementations in two languages (Java and C), with at least three GUI frameworks (in Java, JS and C)... it's a *mess*. If you want elegant, integrated software, don't go anywhere near Amazon. They've never worked that way.
Quote:
Originally Posted by Axanar
Each Kindle firmware update isn't a full rewrite! They compile new updated libraries, use a new wayland display server
|
I'm reasonably sure the Kindle has used directfb and now X11 but never Wayland. Given their degree of dependence on a custom Awesome config that bubbles windows to different layers depending on their WM_TITLE, I'd suspect it'd be a big rewrite to move across to Wayland, too: they'd need a custom compositor at the very least.
(Also, frankly, Wayland isn't stable enough for a device that just has to work. Not yet.)