• 1 Post
  • 334 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • Ubuntu, RHEL and Fedora use it as the default and they are very big distros. Idk if it’s enough but that’s what I know.

    I mean, that’s pretty irrelevant. If you were for example at least comparing the downloads of fedora Vs spins, that would be a beginning of something.

    Idk. KDE was unstable for me and it always has bugs after major releases. They should test things better.

    1. In case it wasn’t obvious: stability is not reliability

    2. So does GNOME, especially when you have a lot of extensions

    3. KDE is pretty crap in both regards

    Personal opinion.

    Is that why every distro comes with vanilla GNOME? Oh wait…

    But hey at least it’s getting better over time.

    Meanwhile over the years KDE got lighter than GNOME while constantly piling on features.


  • the most popular

    Citation very much needed

    one of the most stable DEs on Linux

    Hardly, but I’m guessing you’re thinking of reliability instead. Not really surprising when it’s so stripped down that vanilla GNOME is pretty much unusable. When you extend it, in order to get a proper DE, that goes right out the window.

    That fact makes it especially funny that vanilla GNOME is by far the fattest DE around. How it manages to use up more resources than KDE is beyond me.







  • It’s about 300mb lighter than KDE in my experiences. On 2gb of RAM, that makes a difference.

    And both LXDE and LXQT use half as much RAM as Xfce.

    LXDE is gonna be fine too; but it lacks a lot of the polish that XFCE has. I honestly like both for different things.

    I’d rather be able to open more than 5 tabs than have a fancy UI. That’s why Xfce is on my newer devices, and I install those 2 whenever someone needs an ancient laptop revived.











  • Shareni@programming.devtoLinux@lemmy.mlDecision of Next Os
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    1 month ago

    That’s because of users, not OS… right?

    It’s a factor, but constantly upgrading to the newest version of software does come with risks. I’ve had Arch and derivatives fail to boot on multiple devices plenty of times after an update.

    Some people say that they run arch for years without having any issues, but that’s either extreme luck or bs.

    I love to deal with problems but I don’t want to waste my time.

    You can usually just use a btrfs snapshot to rollback, boot, and try to update later. But there were situations when I had to use arch-chroot, and it can be problematic to install new packages in that situation.

    All setups have tradeoffs, but I’d wholeheartedly suggest a stable distro like MX and nix + home-manager. It avoids all of the previously mentioned issues, and comes with other benefits. Do note that you might need to make or copy a hyprland.desktop file because home-manager can only alter files in your ~.


  • e.g. don’t touch AGPL code unless you also use AGPL

    Just to clear this up: copyleft licenses, GPL variants for example, require the license of your code to equally preserve the freedoms provided to your users, or in other words also be a copyleft license. There are some loopholes like GPL on a server, but be very careful when using copyleft code unless you want to use a copyleft license as well.

    It gets somewhat murkier when you use someone’s code and base yours on that. IANAL, and that’s very much the legal territory. If at all possible, just reuse the original copyright and license and then derive your work (given the license allows that).

    That all depends on the license AFAIK, but IANAL. Most FOSS licenses allow you to do whatever you want while preserving copyright claims, and that includes rewriting or changing the license. GPL forces copyleft, so even if you rewrote it from scratch, you could still be liable if you saw the original code.

    For example I’ve heard that corpos bootleg copyleft code by having completely separate teams doing design and implementation. The implementation team can’t ever see any part of the original code, and they have limited communication with the design team. I think that would also go around the copyright claims as well.

    If at all possible, just reuse the original copyright and license and then derive your work (given the license allows that).

    Or just slap a GPL and subsume everything within a vortex of FREEDOM, and thusly become a true FOSS dude