cancelAll the "memory is cheap" developers can truly shut the fuck up now.
ARGVMI~1.PIFThankfully Linux people don't seem to have that attitude. Even the big bells-and-whistles desktop environment will run comfortably on 4GB.
Ludovic :Firefox: :FreeBSD:@argv_minus_one @cancel back 20 years ago, 4 gb is fing HUGE
RTG-powered Vel@usul while Vel wasn't alive 20 years ago, it's quite certain that low end devices were not using 1920x1080@60 24-bit displays. triple-buffering wasn't used, since there were no fancy smooth animations, etc
using more RAM is often for the purposes of speeding things up and ultimately reducing the load on the CPU/GPU/disk.
macs were triple buffered by default in 2001 (mac os x) windows was triple buffered by default in 2006 (vista)
don't worry it's not that big of a deal.
Curio@cancel
Something is different though. On our laptop almost half the RAM is used by the iGPU driver's RAM spillover. This was not the case 5+ years ago.
That (and websites getting fatter) are the main reason it regularily OOMs.
Got any info/hypothesis on that?
@risc @usul @argv_minus_one
@curiousicae sounds like either a bug or strange settings... vel's iGPU only gets any significant amount of RAM when it's actively using something heavy
@risc @curiousicae @usul @argv_minus_one yeah usually you allocate a small amount of fixed memory for the iGPU in BIOS for software which can't dynamically allocate it for some reason (certain old APIs?) and then allow the GPU driver to carve out more memory for graphics from shared as needed using the proper APIs.
@cancel
Most of the used memory is “GTT” (horrible Linux kernel jargon for “RAM dynamically allocated by the GPU” - took me years to understand that radeontop line).
I think the static assignment is actually for the iGPU, so that it can function without the graphics driver being present.
Seems like its feeling modest right now though (usually GTT is easily twice that) – really doubt AMD fixed anything for a “legacy” GCN 1.0 card in their driver suddenly:
@risc @usul @argv_minus_one
That is a good example of using more RAM to make things faster and smoother. It's just that it became an example earlier than @risc thought (because RAM was already fairly plentiful in 2001).
Like, you know how gamers these days say to run video games in windowed mode instead of full screen to make them run smoother? That's because the window compositor is triple-buffering the game. In full-screen mode, this doesn't happen (unless the game itself does triple buffering).
Ozzelot 
@risc
why in the everloving god did we ever design for more than 1024x768 anyway
@usul @argv_minus_one @cancel
why in the everloving god did we ever design for more than 1024x768 anyway
@usul @argv_minus_one @cancel
As someone who is very much enjoying his new 3840×2160 screen, it's because I can see *everything* on this huge damn screen. I love it so much.
Now if apps could go ahead and stop wasting space on unnecessary padding, that'd be great. I'm using a desktop with a mouse, not a phone!
Although I do have a touchscreen laptop, so… 🤷♂️