Memory is there to be used. Have at it.
If I've just restarted the machine, sometimes I can launch Chrome.
Chrome print preview never renders about 90% of the time when I am able to launch it. Firefox, no issues.
On a large complex page, when Chrome does manage to launch and print preview does load, it takes tens of seconds to render. Firefox, no issues.
I pretty much just use Chrome when I absolutely have to do a cross-browser test these days.
BTW, a Chrome-tangential annoyance is that the code process in VSCode which is basically an embedded browser sometimes runs wild sucking up gigabytes of RAM on another VM dedicated pretty much just to VSCode (and a couple of other minor tools on a lightweight desktop). The irritating thing there is that due to, apparently, a limitation of the blink embed they are using, you can't restrict the RAM available to VSCode to any number (even 100% of system ram) so you basically have to wait for the oomkiller to kill it, or run a parallel monitor to kill it once it sucks up too much ram.
Many different users have many different use cases.
What you're basically saying is: It works OK for me, so the fact that it doesn't work for you is insignificant.
That said, these days I only use Chromium occasionally, so this could have changed over the least few years.
If you are going to make such a wild claim, you should back this up with data, your “feelings” are not enough.
I wouldn't care one bit if the GUI was rendered in immediate-mode software rendering, if it worked. I interact with websites far more.