> This always made sense to me because of the multi-process architecture of Chrome, but I've never seen it myself. If you have hundreds of tabs in Chrome, you'

> This always made sense to me because of the multi-process architecture of Chrome, but I've never seen it myself. If you have hundreds of tabs in Chrome, you'd have hundreds of processes. In this case, Firefox used to perform much better with lots of tabs because it didn't spin up a process for each one. The downside of this model is that a crash would take down all your tabs in Firefox rather than a single tab in Chrome. Of course, now Firefox is also multi-process. I can never have hundreds of tabs open in Chrome because the UI just doesn't handle that nicely. In Firefox I use multi-row tabs and can comfortably have 40 tabs open without issue.