Thread: Kobo Firmware 3.11.0
View Single Post
Old 10-26-2014, 09:38 PM   #214
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Anak View Post
Most of the bugs/issues you refer to are 'implementation bugs' by Kobo as they have nothing to do with the render engine (here: RMSDK).
If the same bugs and/or issues also surface on Sony, Icarus, Bookeen and other ereaders that use RMSDK then those bugs are RMSDK related.
If not, those bugs, issues or problems are created by Kobo.
Are any of these using the same version of the RMSDK as Kobo? Kobo is now using RMSDK 10, but not the latest build. Up until they upgraded to this earlier in the year they were using a very version that was at least two years old. The impression I have from discussion of bugs here is that Sony was using a newer version than Kobo had been using but, I don't think they are using RMSDK 10. Because each of the readers are probably using different builds of the RMSDK, if not different versions, then it is hard to compare the bugs between them and direct blame.

Before anyone jumps on me about this, it is Kobo's responsibility to fix the bugs in the firmware. But, because they rely on libraries and code from other sources, that can make it impossible to do quickly. If a bug is reported and Kobo discover it is in a library they get from elsewhere, they have to report it to that developer and wait for a fix. When they receive the fix they have to test the updated library. But, they don't just have to test the bug was fixed, they have to test all the rest of the function in the library that they use. That is a lot of work. So, they probably wait for a few bugs in the library to be fixed and do one round of testing for all of them. How long they wait would depend on the severity of the bug. A bug that makes the device reboot each time it was used, will be rolled out as soon as the fix is available (and has caused Kobo to withdraw an update). But, a bug such as "no hyphenation on the first line of a paragraph if the line is indented" is not going to make them take the risk and expense of an update to the library. Ten or twenty bugs like that might.

So, of course, Kobo go on developing new features. They can't fix the bugs that are out of their control. They do fix those that are in their control. And they add new features that they think are a "good idea".
davidfor is offline   Reply With Quote