6 ms·

Whut? It didn't get any faster, it's just more aggressively lazy loaded now. This is breaking the very use case of people who have 100+ tabs; they want stuff to

Whut? It didn't get any faster, it's just more aggressively lazy loaded now. This is breaking the very use case of people who have 100+ tabs; they want stuff to be there when they click on it.

ehsanu1 9y ago
As a many tabs user, I don't agree. The use case is more like a more visible bookmark, with history. Any tabs commonly used will already be loaded, and it is fine to lazy load tabs that are rarely used but kept open as reminders. It's definitely a much better experience than waiting 5 minutes after startup for the CPU activity to die down.
mkl 9y ago
Not true. On most days I visit <30 open tabs (out of hundreds). I'm happy to wait for a page to load when I visit an old one, and I'd really like my browser to unload pages I'm not actively using (but give me an override). Tabs for me are like much more convenient bookmarks.
bobcostas55 9y ago
This is completely right. None of those tabs are doing anything, they're literally just holding a URL and waiting to load it when the user switches over to that tab. It's not a tab, it's a bookmark. I've got a gazillion tabs open on Chrome right now and guess what, they're all actually open.
- yoasif_ 9y ago
  > None of those tabs are doing anything, they're literally just holding a URL and waiting to load it when the user switches over to that tab. It's not a tab, it's a bookmark. The tabs store state too, so they aren't just bookmarks - I just closed the browser with just your quoted text in the reply form, and upon restart, the text was restored. Chrome does seem to work this way as well, but loads all tabs by default instead of lazy loading when a user navigates to the tab. https://wiki.mozilla.org/Firefox/session_restore#Restoring_sessions https://wiki.mozilla.org/Firefox/session_restore#Restoring_s...
kenhwang 9y ago
It also loads a cached version of the page almost exactly as it were when the browser shut down. Unless you were AFK farming Cookie Clicker, it works just fine.
glandium 9y ago
Things have been lazy loaded on startup since Firefox 13: https://bugzilla.mozilla.org/show_bug.cgi?id=711193 https://bugzilla.mozilla.org/show_bug.cgi?id=711193 but the feature itself is much older. The problem was that the xul/xbl code creating the tabbar was still doing a lot of work for the not-yet-loaded tabs.
- revelation 9y ago
  Yes, it's "it's just more aggressively lazy loaded". Unless you are trying to say it's now not doing less work because it's 1) lazy loading but because 2) they don't know how to implement a tabbar and should have used some native component like Chrome.
  - Dylan16807 9y ago
    I wouldn't call it "more aggressively". The lazy loading is the same, but they fixed the UI code around it.
Manishearth 9y ago
I often have ~100 tabs open, and I have a habit of hitting ctrl-tab and letting it cycle as a fidget. The first cycle is not smooth because there's noticeable aggregate loading, but it's able to cope just fine after with a lot of tabs completely loaded. This has improved a lot rather recently. And when I click a lazy loaded tab after startup there's no noticeable load for the individual tab, it's right there when I click it. It's only when you force-load all the tabs that load times become visible, but that's to be expected.

Whut? It didn't get any faster, it's just more aggressively lazy loaded now. This is breaking the very use case of people who have 100+ tabs; they want stuff to be there when they click on it.

ehsanu1 9y ago

As a many tabs user, I don't agree. The use case is more like a more visible bookmark, with history. Any tabs commonly used will already be loaded, and it is fine to lazy load tabs that are rarely used but kept open as reminders. It's definitely a much better experience than waiting 5 minutes after startup for the CPU activity to die down.

mkl 9y ago

Not true. On most days I visit <30 open tabs (out of hundreds). I'm happy to wait for a page to load when I visit an old one, and I'd really like my browser to unload pages I'm not actively using (but give me an override). Tabs for me are like much more convenient bookmarks.

bobcostas55 9y ago

This is completely right. None of those tabs are doing anything, they're literally just holding a URL and waiting to load it when the user switches over to that tab. It's not a tab, it's a bookmark. I've got a gazillion tabs open on Chrome right now and guess what, they're all actually open.

yoasif_ 9y ago
> None of those tabs are doing anything, they're literally just holding a URL and waiting to load it when the user switches over to that tab. It's not a tab, it's a bookmark. The tabs store state too, so they aren't just bookmarks - I just closed the browser with just your quoted text in the reply form, and upon restart, the text was restored. Chrome does seem to work this way as well, but loads all tabs by default instead of lazy loading when a user navigates to the tab. https://wiki.mozilla.org/Firefox/session_restore#Restoring_sessions https://wiki.mozilla.org/Firefox/session_restore#Restoring_s...

kenhwang 9y ago

It also loads a cached version of the page almost exactly as it were when the browser shut down. Unless you were AFK farming Cookie Clicker, it works just fine.

glandium 9y ago

Things have been lazy loaded on startup since Firefox 13: https://bugzilla.mozilla.org/show_bug.cgi?id=711193 https://bugzilla.mozilla.org/show_bug.cgi?id=711193 but the feature itself is much older. The problem was that the xul/xbl code creating the tabbar was still doing a lot of work for the not-yet-loaded tabs.

revelation 9y ago
Yes, it's "it's just more aggressively lazy loaded". Unless you are trying to say it's now not doing less work because it's 1) lazy loading but because 2) they don't know how to implement a tabbar and should have used some native component like Chrome.
- Dylan16807 9y ago
  I wouldn't call it "more aggressively". The lazy loading is the same, but they fixed the UI code around it.

Manishearth 9y ago

I often have ~100 tabs open, and I have a habit of hitting ctrl-tab and letting it cycle as a fidget. The first cycle is not smooth because there's noticeable aggregate loading, but it's able to cope just fine after with a lot of tabs completely loaded. This has improved a lot rather recently. And when I click a lazy loaded tab after startup there's no noticeable load for the individual tab, it's right there when I click it. It's only when you force-load all the tabs that load times become visible, but that's to be expected.