Its even worse when you force Firefox to use wayland its icon doesn’t even show.

Edit: Oh since everyone now is confused; I only have the flatpak version of Firefox installed yet it doesn’t use the pinned icon and doesn’t even use the firefox icon under wayland at all.

  • BeigeAgenda@lemmy.ca
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    1 年前

    Using the word OS puts across my point, because when you start packaging your toolchain with glibc and whatever libs you need for your application, you end up with a good part of the Linux file system. Yes there’s missing services and so on but they could run if needed.

    It’s not a virtualization joke, it’s more of a “we put flatpak in your flatpak so you can flatpak while you flatpak” recursion joke.

    • qaz@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 年前

      Most system libraries are included in runtimes that are shared among applications.

      • BeigeAgenda@lemmy.ca
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        1 年前

        Sounds more and more like flatpak is a distribution atop of a distribution.

        Good you can share libs, although I can’t see sense in sharing more than the absolute basic libs, and even then some applications will need different versions of the basic libs.

          • BeigeAgenda@lemmy.ca
            link
            fedilink
            arrow-up
            1
            ·
            1 年前

            From what I gather nix is more of a next generation package manager than a application container/sandbox which means potential security problems with old libs could be less, or rather they are probably at the same level as rpm/deb.

            I don’t see any problems with rpm/deb/etc. ending up getting the boot by nix or another package manager just because they are better, that’s just evolution.

            As someone said about flatpak/snap that their ‘hidden’ strength is distribution of proprietary software, that’s fine by me if that’s the main usage of them.

            The sandbox feature can be solved by SELinux/docker/and several other ways depending on usecase.

            • qaz@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              1 年前

              Sandboxing is not the main feature of Flatpak/Snap, being able to ship an app for various distributions without having to configure them separately is. Docker/Podman can do that, but then you would actually be shipping an entire distro.

              • BeigeAgenda@lemmy.ca
                link
                fedilink
                arrow-up
                1
                ·
                1 年前

                Regarding docker/podman that’s why I wrote depending on usecase, for servers it makes sense to distribute because of scalability, on a single user OS it does not.

                From what you write I guess that nix does the distribution part of flatpak, so that seems fine, there’s probably a catch/limitation somewhere, there usually is, but it could be an acceptable one.