> If a browsers works fast and doesn't leak memory, one shouldn't care how much memory exactly is used.
That's a big assumption. Realistically speaking, there's only FF, Safari, and Chrome. FF leaks like crazy (sometimes on it's own but sometimes it could be a plugin). Safari doesn't support all the plugins I use and Chrome may but I'm don't like their dev console layout. And if you don't see how much mem is being used, you have no way of telling if a newly installed plugin just caused a memory leak (unless it just totally prevents you from using the browser).
That's a big assumption. Realistically speaking, there's only FF, Safari, and Chrome. FF leaks like crazy (sometimes on it's own but sometimes it could be a plugin). Safari doesn't support all the plugins I use and Chrome may but I'm don't like their dev console layout. And if you don't see how much mem is being used, you have no way of telling if a newly installed plugin just caused a memory leak (unless it just totally prevents you from using the browser).