• 0 Posts
  • 15 Comments
Joined 2 years ago
cake
Cake day: December 5th, 2023

help-circle

  • But kde applications use even more space with the title bar, menu bar and tool bar. Even if you disable the toolbar and menu bar, there’s much more padding in kde applications resulting in the content area being significantly smaller. I just compared Kate to gedit and the new gnome text editor and it’s not even close. The gnome applications are much more compact.

    I’ve been seeing people complain about header bars being “huge” for years, but every time I actually do a comparison, the header bar application turns out to be more compact than the alternative.

    The only issue with gnome in that area is their antagonism towards themes, as themes can easily fix any size possible problems, but the newest default theme is quite reasonable. I used to have custom CSS to shrink the header bars, but it’s no longer necessary.

    That being said I recently switched to plasma as well, as gnome’s forced Wayland transition resulted in way too many workflow issues and bugs. But I just configured plasma to work like gnome-shell and I’m continuing to use gnome applications.




  • I was wondering if your tool was displaying cache as usage, but I guess not. Not sure what you have running that’s consuming that much.

    I mentioned this in another comment, but I’m currently running a simulation of a whole proxmox cluster with nodes, storage servers, switches and even a windows client machine active. I’m running that all on gnome with Firefox and discord open and this is my usage

    $ free -h
                   total        used        free      shared  buff/cache   available
    Mem:            46Gi        16Gi       9.1Gi       168Mi        22Gi        30Gi
    Swap:          3.8Gi          0B       3.8Gi
    

    Of course discord is inside Firefox, so that helps, but still…



  • About 6 months ago I upgraded my desktop from 16 to 48 gigs cause there were a few times I felt like I needed a bigger tmpfs.
    Anyway, the other day I set up a simulation of this cluster I’m configuring, just kept piling up virtual machines without looking cause I knew I had all the ram I could need for them. Eventually I got curious and checked my usage, I had just only reached 16 gigs.

    I think basically the only time I use more that the 16 gigs I had is when I fire up my GPU passthrough windows VM that I use for games, which isn’t your typical usage.




  • Well personally if a package is not on aur I first check if there’s an appimage available, or if there’s a flatpak. If neither exist, I generally make a package for myself.

    It sounds intimidating, but for most software the package description is just gonna be a single file of maybe 10-15 lines. It’s a useful skill to learn and there’s lots of tutorials explaining how to get into it, as well as the arch wiki serving as documentation. Not to mention, every aur or arch package can be looked at as an example, just click the “view PKGBUILD” link on the side on the package view. You can even simply download an existing package with git clone and just change some bits.

    Alternatively you can just make it locally and use it like that, i.e. just run make without install.


  • Aur and pacman are 90% of why I use arch.

    Also fyi to OP: never install software system-wide without your package manager. No sudo make install, no curl .. | sudo bash or whatever the readme calls for. Not because it’s unsafe, but because eventually you’re likely to end up with a broken system, and then you’ll blame your distro for it, or just Linux in general.

    My desktop install is about a decade old now, and never broke because I only ever use the package manager.

    Of course in your home folder anything goes.



  • Not sure what you’re on about, most package managers have a literal database of most package manager installed files. Debian and derivatives have dpkg --verify or debsums to verify the files, arch has paccheck, I’m sure other distros have something similar. And fixing them is just a matter of reinstalling the package, which you can do from a chroot if the system won’t boot.

    Or you can just run your system on a checksumming FS like btrfs which will instantly tell you when a file goes bad.