| || |
Re: "Lazy List" file?
You're right in that it's a cache, but you completely misinterepreted the term lazy list. It's got nothing to do with being a lazy developer and not bothering to figure out what goes where. Lazy list and Lazy loading means that an app loads images asynchronously.
Originally Posted by kryptonite_2448
Take a twitter client as an example. The avatars are all on the web, the app doesn't pre-download them. However, as you scroll, the app downloads them in the background, and when you are done downloading, you pop the image in. The alternative to lazy loading is stop scrolling while the image downloads, and you get a jittery stutter filled mess. Ironically, lazy loading is actually more work the non-lazy loading. It then caches that file for later, so it doesn't have to download it every single time, and can pull items locally, which is much faster and more efficient. Since you usually lazy load stuff in a list, those lists are called lazy lists.
In short, no well written application should rely on the lazy list to be there. They certainly aren't on the first instance. Deleting them shouldn't hurt, but odds are, file will come back. The more you know and all.