News for hackers. Stuff that matters.
Re:State of web browsers in 2018 by seba_dos1 on Tuesday December 11, 2018 @10:37AM (#18655958)
I have 8GB RAM. It doesn't matter to me that Chrome would be faster if it could eat 4 times the whole RAM I have - what matters is that it's not.

Also, it's a pretty weird test case to compare performance, probably not related to anything that actually matters. What's more, Firefox tries to style the drop-down to match with the system UI, while Chrome doesn't even bother.

Re:State of web browsers in 2018 by Semaphor on Tuesday December 11, 2018 @05:12PM (#18659461)
> I have 8GB RAM. It doesn't matter to me that Chrome would be faster if it could eat 4 times the whole RAM I have - what matters is that it's not.

I specifically said that I can see it being a problem in low ram cases.

> Also, it's a pretty weird test case to compare performance, probably not related to anything that actually matters.

This is not some random benchmarks. Both of these problems are things that I regularly encounter on actual websites. And it's great that FF styles it, but I'd rather have performance than system appropriate dropdowns.

Re:State of web browsers in 2018 by seba_dos1 on Wednesday December 12, 2018 @09:52AM (#18664354)
The only reason 8GB RAM can be considered "low" instead of "appropriate for most workloads" is Chrome.
Re:State of web browsers in 2018 by Semaphor on Friday December 14, 2018 @07:20PM (#18686124)
I don't even run Chrome outside of testing compatibility. I do run Visual Studio, often multiple instances. Right now I don't, only FF, a few apps and Stellaris (which only uses around 500 MB), yet I'm still at nearly 16GB of Memory usage. 8GB might be enough for many (most?) people, but not for me, and it has nothing to do with Chrome.
Re:State of web browsers in 2018 by seba_dos1 on Sunday December 16, 2018 @05:29AM (#18692522)
I also sometimes long for more RAM, but those situations definitely aren't what can be sanely considered "most workloads".