I never understood why people got so concerned with the memory consumption of their programs.

The "RAM not used is RAM wasted" argument doesn't work if you have a program eating up way more RAM than it should.

Chrome being a fucking bitch eating all RAM isn't excusable because you should use most of your RAM anyway, that's like saying you have a locker and should just fill it with garbage because otherwise it's wasted space.

Chrome runs fine on low-memory systems.

Except here's the thing: It doesn't. It has RAM issues.

Can you load 30 tabs at once without lag? No.

Proving my point.

But you can't do that in any browser.

I can do that in Firefox. Keeping 30 pages in RAM is easypeasy. If you were talking about loading all the pages at the same time, the bottleneck isn't RAM but processor and internet connection.

But on systems with tons of memory, the entire point of having that memory is to use it.

Yeah, but that doesn't excuse a program from using more RAM than it should.

So stop looking at your RAM usage and worrying about it.

No. Worry more about it. If a program is a memory hog, it needs to be solved.

Also the vast majority of RAM issues are the result of crappy website developers, not the browser.

False, Chrome is really the issue here. This has been proven on many occasions, this issue isn't new. Don't blame websites for the faults in your browser.

The browser is just a platform upon which their code runs.

It isn't "just a platform" as if that platform can contain no flaws and everything is on the website. It's not. Chrome is evidence of that.

You don't blame the compiler if your program runs like crap.

Correct: You blame the program if the program runs like crap. And Chrome runs like crap. So you blame the program.