4 ms·
A lot of problems are actually really simple if you "just" do caching properly. But, you know what? In general, caching is really hard to do properly. I think t
by silentbicycle 18y ago
A lot of problems are actually really simple if you "just" do caching properly. But, you know what? In general, caching is really hard to do properly. I think the problems with the back button stem from ambiguity in what back actually means. Does it revert a form transaction? Does it restore the cached value of the previous page? Does it go back to the previous URL, updating the content? Since the web uses a stateless protocol, it's unclear to what extent the cache is still valid.
(Also: Does anybody else find articles with large, semi-relevant images between nearly every paragraph to be incredibly irritating?)
- dejb 18y agoI think the description provided in the article is pretty unambiguous. Perhaps other people might want different behaviours but what was described is the article is exactly what I want. I don't care if the cache is valid. I don't care if the webmaster thinks the page needs to be updated every 10 seconds. All I want is the previous page exactly as it was when I last viewed it. It's my browser and it should do what I want. If the webmaster is relying on browser behaviour to ensure I don't resubmit a form then frankly they are asking for trouble.
- ggchappell 18y agoAgreed. And I think his observation on back vs. browser tabs is very insightful. When browsing links, as on HN, I always open a new link in a new tab. And I think the reason is exactly what he says: I don't trust the back button to get me back to the right place quickly. Killing a tab does do that, and so I use tabs.