I get the idea behind it for sure but why use our available ram for this? I thought whatever init functionality would just wipe clean /tmp at boot.
Right now what I'm looking at is that if a system has 16gbram KDE Neon uses half of it for /tmp.
The thing is applications could output to /tmp for a plethora of reasons that could maximize that. Whether you are a content creator or processing data of some sort leaving trails in /tmp the least I want is my ram being used for this thing regardless.
Basically if you drop-in a 10GB file in /tmp right now (if your setup has tmpfs active) you will see a 10GB usage in your htop. Example in https://imgur.com/a/S9JIz9p
I'm not here to pick a fight but as a new KDE Neon user I'm scratching my head on the why after years in Arch Linux.
*-display
description: VGA compatible controller
product: Lucienne
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:03:00.0
logical name: /dev/fb0
version: c2
width: 64 bits
clock: 33MHz
capabilities: vga_controller bus_master cap_list fb
configuration: depth=32 driver=amdgpu latency=0 resolution=1920,1080
I'm using archlinux with plasma 5 & wayland. From time to time it just starts flickering for some reason...
If I need to change drivers just let me know. I don't game or do anything graphical on this laptop. Only software development on vscode and chatting.
@lumirell
@lemmy.kde.social