Quote:
Originally Posted by johnnyb
1. iirc the bug started showing with the first Aura One firmware
2. and 3. the bug has been reported early, but has not been fixed for months
In general: If the Kobo firmware did not come with so many bugs in general, less time would be required to fix what you call a minor bug. Basically what you're saying is that it takes Kobo months to fix a minor feature because they need all of the other time to correct more serious problems. If a software (and if we are talking about December '17 then we are not talking about anything like a .0 release at all) has that many problems after over a year (release version for KAO 'til December '17) of work on the software, then the development team truly has some serious problems. Alternatively, it could of course always mean that Kobo generally invests very little effort in bug-fixing (and that cannot be attributed to the fact that they actually did not introduce any new features – save the new homescreen, the current firmware is actually a stripped down version of version 3.1x).
|
You're not going to like this answer but I'd bet it's reality. Kobo will have a pretty good idea of what percentage of Kobo users have stats turned on (from those who sync with Kobo regularly). If that percentage is tiny, the business reality is that no matter how simple the fix may look, it's not going to get much attention because they can get a bigger bang for their buck elsewhere. As a user does that suck? You bet, and it drives me nuts when I see it, but I can also understand it.
Also, what looks like a simple fix may morph into something a whole lot more complex. Maybe they know what broke it, but the break was caused by a change that make something else work much better. So maybe they can't just turn back the clock because they then lose the much bigger gains that they got when they broke this.