Much earlier, before Covid, Chromium and Firefox already have automatic unloading (discarded entirely from RAM, the page will reload when you open it again) but it's only triggered on low RAM situation. I'm perfectly aware of that behavior because every time another app is hogging the RAM, I'd notice it from the constant reloading when I'm browsing.
Its a user choice and should be a user-facing knob because there are times it is inappropriate for use, such as in safety-critical circumstances, certain realtime realities, and so on. It should probably be on by default for desktop Linux, but off by default for every other application a distribution may be targeting ...
Do Shift+Esc and watch how large the GPU memory usage is. Often 2/3 to 50% of your actual tab usage.
Ironically, its not the closing of tabs that bothers me, but the fact that tab order changes, what slows my productivity/muscle memory down. And its the same reason for a lot of people why they keep tabs open.
I never understood why we do not have a basic snapshot / sleep that offloads a tabs memory on disk (and dumps the GPU memory), aka a ghost tab. And fast loads when you view the tab. Sure, there may be a small delay but it can save so much memory, while people can keep their tabs open/organized.
Some extensions try to mimic that but its often a crude solution because they do not have deeper access to the webview2 engine.
In Firefox there's about:unloads where you can suspend tabs in I believe LRU order. I'd really like to see this as a default option (like: only keep N tabs active). Maybe there's an extension for that.
Yes, macOS has had it enabled by default since OS X Mavericks 10.9, released in October 2013. I’m surprised some desktop Linux distributions still require manual configuration to enable it.
For browser tabs, though, I think a better solution is automatic tab closing, using something like the Tab Wrangler extension for Chrome. Collecting tabs comes naturally; we’re much worse at closing them.