I suspect a few people on HN will be reluctant to see their role in this arrangement. ducks
We built really powerful computers and decided the best way to use them was to run web apps consisting of a poor performance scripting language with a poor performance visual-rendering language and half the people who build with it seem to think that anything done in a web browser is free.
"Modern" CSS for even a simple site is pretty silly. So many horribly inefficient rules, sometimes dozens of levels of overwriting properties, etc. And gobs upon gobs of Javascript that does very little but is constantly running, checking input boxes, animating every tiny little detail, doing things that can be done without Javascript, etc.
I have better system performance when running a Windows 7 VM, a semi-bulky image editor, or compiling the kernel than I do with a few bulky webapps in Firefox. And this is on a desktop built just 4 years ago.
I have a light-weight Linux setup that uses 80MB of RAM after logging in. It has 1GB of RAM. I can't run GMail and Facebook Firefox and browse the Internet at the same time with minimal open tabs. It's sad.
I know that some newer frameworks take advantage of GPU features (actually I used to work as a dev in the Windows org) but guess what, GDI is still faster.
As a data point: Safari is using 600+MB now with just HN and GitHub open. It's using more memory than all the other apps (editor, terminal, mail, Rdio, Skype) combined. 600MB is not much by today's standards, but comparatively, is ridiculously wasteful. It's a damn CD.
Hope the Mavericks update improves this a bit since I'm short on RAM on this machine (4GB).
My MBA has 4GB and I constantly forget, because it is enough, and I am constantly surprised that it doesn't have 8GB.
All modern web browsers save and restore sessions across restarts.
I always up-to-date Firefox, so hopefully the memory leaks are minimal. I reboot my Linux machine every month-ish and don't exit Firefox unless necessary. I always keep a few "app" tabs pinned, only a couple of them are heavy. I have 4GB of RAM and turned swap off for an experiment. Sure enough, after a couple weeks of browsing and keeping about 25 tabs open, Firefox's memory consumption would creep up and up and eventually it would crash.
I can only guess/hope that there are memory leaks involved.
Why should they? If a tab's "dormant", the browser can just quiesce JS timeouts and let the tab's memory get swapped out. Not a problem anymore.
That most (all?) web browsers don't do this currently isn't the user's fault.
Regular users don't know or care about memory management, they don't even close old windows or tabs, its about convenience. That's not a problem in mobile where the need is the mother of invention so mem management is automatic and chrome reopens the tabs you had by itself, but in a desktop environment (specially windows) one wrong click and the session restore in chrome wipes your previous session.
But it was cheap, cheaper than an unlocked iphone and it gets the job done so its ok for her.