News for hackers. Stuff that matters.
Re:Flow browser passes the Acid tests by Beldin on Saturday June 13, 2020 @01:04PM (#23510838)
On a related note, i once came across the notion that free memory isn't doing anything for you.

It's kind of obvious and does not at all explain chromium's lower bound of memory usage. But: if Chromium runs better with more memory and no other process is using it: please take it!

That is what it's there for, after all.

Re:Flow browser passes the Acid tests by gibolt on Saturday June 13, 2020 @01:31PM (#23511065)
This is fine, until another application needs it. Then it becomes a power struggle for the throne, and both sides lose.
Re:Flow browser passes the Acid tests by vbezhenar on Sunday June 14, 2020 @11:53AM (#23518632)
That's not correct for any modern OS. Free memory is used as a disk cache, so your computer is significantly faster with more free memory.

Well, not as significantly now, with SSD everywhere, but still faster.

Re:Flow browser passes the Acid tests by Dylan16807 on Saturday June 13, 2020 @04:47PM (#23512567)
If it would actually detect that, it could be great.

But I have a chromebook with 4GB of ram, and it often struggles to keep a particular set of 3 expensive tabs open because it runs out. It's definitely not reacting to memory pressure by being less greedy.

Re:Flow browser passes the Acid tests by plerpin on Saturday June 13, 2020 @10:30PM (#23514631)
Your pages might have huge JS heaps allocated or contain supersampled assets.