View Single Post
Old 10-04-2012, 04:14 PM   #4
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 4,889
Karma: 4492229
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2
To be completely fair, moving from the crappy FAT32 userstore to a proper ext3 internal partition and a slightly more effective, if complex, backend probably accounts for the fact that, on these new devices, collections handling is slightly less likely to murder the performance of the Kindle homescreen, especially on devices with a lot of content/collections. I's at least much more tightly wound into the system, compared to the 'slapped-on' feel of the feature added on FW 2.5 and still used on 3.x & 4.x.

(Meaning I'm of the mind that the move wasn't just to piss us off, there was a legit performance concern behind it. Although, maybe not terribly well thought out, because it can effectively softbrick a Kindle on very large (~5K) libraries...).

Last edited by NiLuJe; 10-04-2012 at 04:20 PM.
NiLuJe is offline   Reply With Quote