4 ms·
Can anyone suggest why this might be the case (presuming that it is true)? It seems to be much more work to hide the image vs. simply deleting it, so I'm guess
by justinsb 13y ago
Can anyone suggest why this might be the case (presuming that it is true)? It seems to be much more work to hide the image vs. simply deleting it, so I'm guessing that there is a reason...
- jijji 13y agosounds like developers pre-occupied with style and fancy coding rather than efficiency and performance.
- potatolicious 13y agoI haven't seen the Snapchat codebase at all, but my knee-jerk suspicion is use of an off-the-shelf image cache. Caching images on the device is basically a universal problem for mobile apps. It improves responsiveness and prevents unnecessary network usage. As such, there are open source libs that do all the boring heavy lifting for you. Most images caches also don't hold sensitive images, nor do they really expire. In this case, you may have deleted the database row around the post, but the image cache still has the image on-disk.