5 ms·

> modern browsers are so stupid that they reload all the tabs when you restart them. firefox does not do this.

• delecti 10y ago
  Additionally, it's debateable whether that's a bad default to begin with.
  • chetanahuja 10y ago
    Oh everything is debatable if you're inclined to debate. But as far as user experience goes, that shitty default (with no way to disable it) on chrome is a pretty one-sided debate.
    • Hondor 10y ago
      The point of being debatable is that it's not obvious what the best answer is. If it didn't load all the tabs, then you'd see an outdated version of the page when you clicked on a tab, or it'd load when you clicked on it, forcing you to wait right at the moment when you want it immediately. Reloading all tabs sounds like the best option for people who use tabs to temporarily use several websites at once. That's what I do - never having more than half a dozen and closing them all when I'm finished on the computer. For people who use them in place of bookmarks, it would be better not to load them.
      • chetanahuja 10y ago
        a "debatable" option shouldn't be the only option. Which is the case in chrome. No way to disable that behavior either from the command line or from the settings UI.
        • mentando 10y ago
          Well, it is debatable, if it is good. For some it is obviously not, but for others it is a good default. What's bad is that it cannot be changed. That is not debatable.
        • delecti 10y ago
          Google has been moving quite a bit in the direction of fewer and fewer options. I may like it the way things are, but I do agree it should be an option.
  • vacri 10y ago
    "load all tabs" on restart is a terrible default for people who like to have dozens of tabs. I can't see any reasonable argument for it, for those users.
    • iopq 10y ago
      I actually want this to happen in all of my tabs because I want them to UPDATE. This is why I keep them open in the first place.
      • zeveb 10y ago
        I think that the mechanism I suggested elsewhere would handle this best: each tab's complete state (DOM, JavaScript &c.) should be marshalled to disk at quit (and checkpointed periodically, in case of crashes); on startup, all tabs are loaded and their DOM & JavaScript contexts restored. If a tab's context had it set to update periodically, then that periodic-update context would be restored; if not, then the remote server would never be contacted until and unless the user hits reload. This seems so obviously correct to me that I wonder what I'm missing.
        • kuschku 10y ago
          > This seems so obviously correct to me that I wonder what I'm missing. You are missing that > should be marshalled to disk at quit is not easily doable.
          • zeveb 10y ago
            Why not? The DOM is, ultimately, just HTML. The VM state is just data in RAM, which should be eminently serialisable. I'd think it's the sort of thing which ought to be child's play.
            • kuschku 10y ago
              The VM state isn't that easy when you remember that JS can keep open sockets to other things, can launch processes, etc. Sure, you could find a way to serialize it, but that'd be a lot harder — you can't hust go back to halfway the middle of receiving something through a socket.
  • rtpg 10y ago
    It might not be a bad default, but here's the alternative: load a tab only when you've signaled you're going to look at it. Even if you have 300 tabs open, your browser won't try loading everything at once, so you can do what you want.
  • flukus 10y ago
    It drives me mad when chrome does this, there is a noticeable delay between switching the tab and rendering for the first time.
  • progval 10y ago
    It allows me to quickly open a new tab and do something if I am in a hury. Otherwise, I press Ctrl+Tab long enough to go through all the tabs and wait for it to load them all.
• thesmallestcat 10y ago
  Firefox does something else stupid though: If your browser crashes/freezes (which, because no multi-process, 99.999% of the time is caused by bad JavaScript on a given page) it does the helpful thing of restoring your tabs. So now it's a race to close the offending tab before it can fully load.
  • sp332 10y ago
    It gives you a "restore session" page where you can choose which tabs to re-open.
• zeveb 10y ago
  It does, however, reload the tab's contents when you switch to it. The smarter thing to do IMHO would be to marshal the DOM & JavaScript context to disk, and load that, only reloading from the original page if the user clicks 'reload.' I don't think that the disk space necessary to cache all this is scary, since after all the whole thing has to fit in memory anyway, and disks are order of magnitude larger than RAM.