3 ms·
I understand that pages can change their state without user interaction, but shouldn't the browser only write to disk when that actually happens? The browser ha
by CoryG89 10y ago
I understand that pages can change their state without user interaction, but shouldn't the browser only write to disk when that actually happens? The browser has to be able to detect when these changes happen right?
I understand that it's probably not an issue for most users/SSDs. However, if I open just a static HTML file and leave it idle, I don't think the browser should be continually writing to disk. If it is, then to me that is a bug.
EDIT: Also, it seems like when I remember restoring a browser session after a crash, all the tabs get reloaded, not restoring the page state, just the tabs/URLs (ie. browser makes new request(s) for each restored tab). I usually use Chrome though, not sure if this has happened to me on Firefox.
- heinrich5991 10y agoIn Firefox, it might look like it's doing requests, however it'll show me a days-old HN newspage that it cannot possibly get from the server.
- gcp 10y agoIt won't write to disk with static pages. But most of the web doesn't fit that description, and you're bound to have a tab open that does something in the background. Yoric pointed out here that not being able to save tabs individually is a weak point of the current implementation.
- kalleboo 10y ago> but shouldn't the browser only write to disk when that actually happens The problem is that it's happening continuously. Any page with analytics or ad engines (I'd guess easily 95% of the top visited web) is continually logging how long you've been on the page, scroll position, idle time, etc. And then setting a cookie to remember the session info/last time it was updated. It would be interesting to see what installing an ad blocker would do to these numbers.