Keyoxide: aspe:keyoxide.org:KI5WYVI3WGWSIGMOKOOOGF4JAE (think PGP key but modern and easier to use)

  • 2 Posts
  • 110 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle

  • Wayland and GPU stuff should be very good in endeavor, better than most systems I have seen, better than openSUSE leap and mint certainly. I don’t know fedora however.

    Endeavor has its own base repo, but also the regular arch stuff like aur. The AUR is probably the best source for all those programs that are usually missing in your repo, and since the base stuff is stable in endeavor there is no problem if some random program needs a special version or a manual install sometimes, it won’t affect anything else.
    The AUR is not the main package source for endeavor.
    I don’t know your hardware, but the combination of up to date system components, endeavors focus on just working, and all the shit in the aur (to my understanding flatpak is currently quite useless for drivers) sound like it should just accept any hardware at least as well as other linux distros.

    On a sidenote for flatpaks. There is this long running conflict between stability, portability, and security. The old-school package systems are designed to allow updating libraries systemwide, switching-in abi compatible replacements containing fixes. On the other hand, you have appimage, flatpak, …, which bring their own everything and will therefore keep running on old unsafe libraries sometimes for years before the developers of all those specific projects update their projects’ versions of all those libraries.















  • You can compare total better than per user at these scales.
    Lemmy needs a certain amount of performance to keep up with federation, but once you have all the images and posts and comments you don’t need second versions until you scale to a size that mandates multiple machines. Which I would guess is more in the 6+ digit user range, where you start averaging requests per second not minute.

    In some sense, every lemmy user is a user of your instance via federation. You need to pay the performance for all 100k of us whether your instance has 10 or 10k of those. Local users are just a bit extra demanding on your hosting resources.

    I suspect the bias we see here with larger instances paying a bit more (50-ish instead of 10-ish) is more due to reliability and snappyness than actual performance needs too. You tend to get optional smaller-gains pricier perks you might not go for for a smaller instance.