• 1 Post
  • 337 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle



  • GNOME caches and prefetches everything it may need. Where as KDE will fetch as needed. If you run a memory tool that shows actual memory being used vs Cache, you will see most is cache.

    I have a 14 year old laptop with celeron processor, KDE and XFCE were performing badly, GNOME runs great. My assumption is with all the prefetch the old/slow system CPU/board has what it needs to perform as expected.












  • So Technically No. Our proprietary CAD was only supported and certified to work on RHEL or SUSE. I wanted to test before commiting to a distro. So I went with OpenSUSE leap since it shares SUSE binaries and has same release and service cycle. It installed and functions well on OoenSUSE While not identical to SUSE, I can say all the complaints I saw online of things not working in Linux were working for me. They sort of have to on a paid distro with support, so it seems to carry to OpenSUSE with the same binaries

    1. nVidia hosts a repo specifically for SUSE and OpenSUSE ( probably RHEL too) it meany adding that nvdia url and updating in Yast2 GUI. Everything works, no tearing, no glitches, nVidia app for thermal settings or tweaking.

    2)btrfs works. I saw lots of complaints of people saying btrfs filled their drive, etc. SUSE / OpenSUSE as jobs establishes to monitor number and age of snapshots and remove automatically as needed as well as cleaning tools. It all runs behind the scenes.

    1. patches, people complain they don’t know if a CVE affects them, if they have applied a patch or not, what package etc. On SUSE/OoenSUSE you have several patch, patches, lp commands that show you what has been released, what level and whether your system has it installed, not required, critical etc. Keeping up with CVE and patches is easy.

    I assume RHEL will also have these types of perks to make some aspects easier





  • BCsven@lemmy.catoMemes@lemmy.mlSoftware: Then vs Now
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    18 days ago

    Agreed. Or look at the manual effort, is it worth coding it, or just do it manually for one offs. A coworker would code a bunch of mundane tasks for single problems, where I would check if it actually will save time or I just manually manipulate the data myself.