3 ms·
And nowadays* Chrome unloads "old" tabs from memory, which must be a frustrating user experience for low memory users, open something in a new tab, try to go to
by netsharc 10y ago
And nowadays* Chrome unloads "old" tabs from memory, which must be a frustrating user experience for low memory users, open something in a new tab, try to go to the previous tab, and the browser had to load it again.
* Maybe they've fixed this
Of course it all works on the developer's machine, it has 16GB RAM, full HD screen and a connection straight to the backbone...
- deleted 10y ago[deleted]
- ajmurmann 10y agoWell. To be fair the developer is upset that the MacBook pro doesn't come with 32GB RAM.
- rtpg 10y agoWhat's the alternative in this situation though? If you don't have enough RAM to hold everything you don't have enough RAM. This seems like a decent solution, because the user experience is "wait a bit when loading stale tabs", rather than "have the entire browser choke without being really sure why"