• CethinEnglish
      201·
      19 days ago

      It’s not the ideal solution, but it is approachable and understandable for technically averse users. I think it’s good to have, but I only used it for one package, and that was as a separate Steam install that included an old version of glibc that was used in a particular game’s (Squad) anti-cheat until it updated it.

      It’s good for a stable platform, but each package needs it’s own set of everything, which can be good (like the Steam example above having its own version of glibc instead of using the shared version on my system), it’s a lot of bloat. I’m not using it unless I require it for some reason, but again it’s nice to have around.

      • henfredemars@infosec.pubEnglish
        3·
        19 days ago

        I don’t think Flatpak is going to be compatible with Steam anyway in the long-term because layering container solutions doesn’t generally work very well, and Steam is going to want to use its own solution for better control over the libraries each game uses. Earlier versions used library redirection and some still do.

        • ngwoo@lemmy.worldEnglish
          192·
          19 days ago

          There’s a big chunk of the Linux community that will always want to gatekeep it and push out anything that makes it easier for the layman to use

        • 31337@sh.itjust.works
          79·
          19 days ago

          Wastes RAM and disk space (compared to package-manager installed applications) by storing more libraries on disk and loading them into RAM rather than just using the libraries already installed on the distro. It’s probably better than Snap and Appimage though.

          • henfredemars@infosec.pubEnglish
            61·
            19 days ago

            That is definitely a sacrifice being made here I agree with you. It gives developers more control over exactly how their app runs, but it does mean less storage efficiency.

          • pressanykeynow@lemmy.world
            41·
            19 days ago

            Is it even a problem for a desktop in 2024? Never had an issue with RAM or diskspace. And even for those that have, they can just not use flatpak until they upgrade, no reason to kill it.

            • 31337@sh.itjust.works
              31·
              19 days ago

              I assume the “kill it” comment was a little tongue-in-cheek. On small SBCs, like a Pi, or old hardware, it could be a problem. I’ve seen people with flatpaks taking up 30GB of space, which is significant. I’m not sure how much RAM it wastes. I assume running 6 different applications that have loaded 6 different versions of Qt libraries would also use significantly more RAM than just loading the system’s shared Qt libraries once.

              • pressanykeynow@lemmy.world
                2·
                19 days ago

                I don’t see a problem with Flatpak in this. It does what it’s supposed to do. You find not using it better? That’s great, that option is the default in all of the distributives.

                • 31337@sh.itjust.works
                  1·
                  19 days ago

                  Yeah, I agree. I do use Flatpaks, Snaps, and Appimages sometimes if I can’t find a suitable deb repo/package. Flatpak is the best out of the three because they do try to avoid too much duplication through runtimes. I also use Docker quite a bit, which has similar issues (and benefits).

          • henfredemars@infosec.pubEnglish
            9·
            19 days ago

            Different goals and different designs. Why are there so many Linux distro?

            Snap is proprietary. Appimage does not include distribution and updates. It also doesn’t attempt sandboxing of any kind.

            On the other hand, I find appimage very convenient to use.

  • unskilled5117@feddit.orgEnglish
    461·
    20 days ago

    Great to see progress! Why is it behind their official github releases though? Latest version is 2024.10.2 and not 2024.09.0. It is four releases, meaning more than a month, behind.

  • tomjuggler@lemmy.world
    191·
    19 days ago

    What does this desktop app do that the browser extension doesn’t? I tried the cli extension but it was rubbish…

    • trevor@lemmy.blahaj.zoneEnglish
      9·
      19 days ago

      The desktop app can be used as a bridge for biometrics in the browser extension, but other than that, it basically serves no unique purpose unless and until they add autofill for desktop applications.

    • Lem453@lemmy.ca
      5·
      19 days ago

      I also would like to know what the desktop app is used for?

      I’ve seen apps like xpipe that have direct Bitwarden integration if you want (way too high risk for me but I can see some people using it), but even then it integrates directly to the servers API. When I need an ssh password or something I copy and paste it from the browser extension. I’m curious if I’m missing some functionality by not using the app.

      • Allero@lemmy.today
        14·
        19 days ago

        You’re not, it’s just that sometimes you paste your passwords outside browser, and opening a browser for that is doable, but feels wrong :D

        Also, the app has a more convenient layout as it can afford more screen space.

    • Ryan@programming.devEnglish
      22·
      20 days ago

      Sync that has never broken for me and works on a phone. My attempts at keypass with both google drive and syncthing invariably ended up with me needing to periodically do manual reconciliation. I’ve never had this problem with bitwarden. Also, bitwardens passkey hooks work on iOS. They appear unsupported by keepassium.

    • tuhriel@discuss.tchncs.de
      18·
      20 days ago

      Probably a bit more polished UX (especially for not too tech-savy people)

      but I’d say the biggest difference is integrated multidevice support, either via their cloud or selfhosted…

    • thejevans@lemmy.ml
      101·
      19 days ago

      I cannot access my homelab from my work network, so I cannot sync via Nextcloud. Syncthing would be better, but they just stopped supporting Android sync, which I need. Proton Drive doesn’t sync files on Android. On top of that, I don’t want to deal with sync issues because keepass isn’t designed for syncing like that. I’m not gonna go back to using Google, Microsoft, or Dropbox just for keepass. I’ve considered just keeping my db file on a flash drive, but all of the keepass Android apps I tried won’t automatically detect that the file exists when I plug in the drive.

      If someone has a better way for me to use it, please enlighten me.

      Bitwarden is slowly turning their stuff closed-source, and I hope they don’t turn to shit, but right now it’s what works.