And yet where we are. And why wouldn't I consider those parts of the browser specially not including JS heap from any measure is absurd. I am primarily using C

And yet where we are. And why wouldn't I consider those parts of the browser specially not including JS heap from any measure is absurd. I am primarily using Chrome these days. I just looked at its own report. One of my gmail account tab is using 891M memory. I am not saying it's entirely the fault of the browser but whole web echo system. What you said is actually true that this is the result after millions of dollars worth of effort in trimming the fat. But that only turns it from absurd to actually pitiful. I am not faulting individual developers or just browsers of course. It's from the spec, to the browser, to the web developers but if people don't accept web as a whole for all the fabulous advantage/access they provide which I don't discount is out of control this will never fix. There are fundamental problem here and no amount of incremental improvement will probably fix it. I guess I will rant for a few more years to myself before accepting the status quo. I don't restart my browser or machine for fairly long time and those few long running tabs keep increasing in memory. I also just opened up firefox and loaded up that same gmail account fresh. I think it started off at 350 and 5 minutes later it's over 400MB. Maybe it happened after I switched to web based client fully but I think I never had a desktop mail client that took 400MB memory. I am a server side programmer who isn't really some grand expert in performance (nowhere close) and I work with fat bloated Java but I still know 400MB gets you a long way or it should.