For those skeptical how this can happen, it's the natural situation when two things are true: (a) wanting to create a new browser window when a new "context" i

For those skeptical how this can happen, it's the natural situation when two things are true: (a) wanting to create a new browser window when a new "context" is necessary, rather than navigating away from one's current context, and (b) being in an environment where "contexts" are added more rapidly than they can be fully triaged, delegated, or completed. If you're (1) working on some deep frontend code and previewing it in the browser, then (2) you need to look up how to do a certain thing in React which might require reading multiple documentation and Stack Overflow posts, and in the midst of that (3) need to fix an urgent bug in something you've owned, and you do so but are waiting for CI to pass on the fix, and while waiting for that (4) you also need to unblock a colleague on a question about a specific piece of documentation and send them some Github links but not wanting to close them until they respond: you've just created 4 windows with many tabs open in each. Now, if on top of this you are in a CTO or PM style role in which you need to do a few observability or analytics dives per day to try to understand specific customer situations... each of those may result in a context as well. On this crazy day, you have 10 context windows, each with 4 or more tabs, accumulate during a single day, and you may only be able to fully get through the backlog over the course of the following few days. Probabilistically, there will be a time during certain weeks where you have 160-200 tabs from this workload alone. Tools like https://chrome.google.com/webstore/detail/toby-for-chrome/hddnkoipeenegfoeaoibdmnaalmgkpip?hl=en https://chrome.google.com/webstore/detail/toby-for-chrome/hd... and https://chrome.google.com/webstore/detail/tab-manager-plus-for-chro/cnkdjjdmfiffagllbiiilooaoofcoeff https://chrome.google.com/webstore/detail/tab-manager-plus-f... are extremely useful, but do require that you're willing to suspend your page state, including any state in dev tools or scroll position - so they're simply a way to speed up getting through the backlog of contexts, not a silver bullet. So if you're the one they go to when situations arise, and you can't grow your team as fast as you need... the TL;DR is: if any of this sounds familiar, you will want that 64GB of RAM for your laptop sooner rather than later.