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

help-circle





  • Darorad@lemmy.worldtolinuxmemes@lemmy.worldYeah...
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 month ago

    Yeah, recently I’ve run into 1 game I’ve wanted to play that I just couldn’t (Valorant so probably a better outcome lol) and maybe 2 that had any sort of issue.

    If you’re mainly into competitive games it’s still rough, but otherwise it’s honestly smoother than my friends on Windows often.



  • Darorad@lemmy.worldtolinuxmemes@lemmy.worldSnap out of it
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 month ago

    Yeah, sorry couldn’t resist.

    snaps are very similar to flatpaks and, honestly, is technically better in a lot of ways.

    Snap can be used for basically an entire system, while flatpak is limited to graphical apps. (Ubuntu core is built basically entirely off snaps.)

    Snap is controlled by canonical, and the backend for the snap repo is entirely closed source. I’ve heard snaps are also easier for developers to work with, but I haven’t experienced that side of them.

    Snaps automatically update by default where flatpaks don’t.

    Snaps also get treated as loopback devices when they’re installed, which bloats a lot of utilities. (And they keep a few old versions around which makes it even worse). For example, you could run lsblk and if you’re using snaps like 90% of it will be snaps you’ve installed instead of actual devices.

    Flatpaks are also noticeably faster to start up, which for desktop apps matters, but wouldn’t really matter for a server that’s aiming for a lot of uptime.

    The loopback device issue is the main reason I don’t use snaps. I also like flatpak being completely open, but realistically that doesn’t matter for much. There used to be an open snap store, but that shut down because nobody used it.


  • The easiest way to think of it is flatpaks are AppImages with a repository and snaps are flatpaks but bad.

    That has benefits and detriments. Appimages contain everything they need to run, flatpak’s mostly do, but can also use runtimes that are shared between flatpaks.

    All flatpaks are sandboxed, which tends to make them more secure. AppImages can be sandboxed, but many aren’t.

    Flatpaks tend to integrate with the host system better, you can (kinda) theme them, their updates are handled via the flatpak repo, and they register apps with the system.

    AppImages are infinitely more portable. Everything’s in one file, so you can pretty much just copy that to any system and you have the app.




  • I agree with pretty much everything they’ve said, though I’ve gotten more use out of the swappable parts. I have a desktop I use for things I need a powerful system for, but being able to swap in the GPU when traveling is great.

    When I’m at home I have basically everything on USB C and the empty expansion bay.

    When I travel I swap in the GPU and add an HDMI port and some USB a ports.

    If you don’t have stuff set up like I do I agree it’s mostly just a reparability / upgradeability thing.