• danhab99@programming.dev
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    5 hours ago

    Nix is just across the street sipping tea because it understands what it is and is at peace with the chaotic world around it.

    • stebator@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      25 minutes ago

      I use NixOS and Flatpak (Nix-Flatpak) to install software that is not available in Nixpkgs. Unlike Arch’s AUR, Nixpkgs has fewer popular packages. However, Nixpkgs beats AUR in terms of quantity because many Nixpkgs packages are redundant.

  • Abnorc@lemm.ee
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    7 hours ago

    It’s not about the package management method that we use. It’s about the friends and enemies we made along the way (while arguing about package management.)

  • Phoenixz@lemmy.ca
    link
    fedilink
    arrow-up
    4
    ·
    7 hours ago

    That’s because we are…

    If .y Firefox will once again be updated without asking me and then refusing to open any page without a restart I’ll fucking lose it

    • Sonotsugipaa@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      5
      ·
      3 hours ago

      Wait hold on wait, does that bullshit have something with Firefox being distributed through Snap?

      If it does, I’m going to sn… also fucking lose it

      • mogoh@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        8 minutes ago

        I have bad news for you …

        (TBH I am not sure, but as I remember, this problem was specifically a snap problem.)

  • Fizz@lemmy.nz
    link
    fedilink
    arrow-up
    7
    arrow-down
    2
    ·
    11 hours ago

    Hadn’t snap fixed a lot of the complaints people initially had?

    • blind3rdeye@lemm.ee
      link
      fedilink
      arrow-up
      23
      arrow-down
      1
      ·
      11 hours ago

      Probably, but the stink will linger for quite a long time.

      There’s a burger place near my house that I use to go to almost every week. But then the quality started going down, and I stopped going there. That was two years ago. Maybe they fixed the problems, but I’m not going to know - because I no longer go there. Snap is like that.

    • UnfortunateShort@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      10 hours ago

      I think the main complaint is that it seems like Canonical is trying take control of Linux packaging. Don’t they handle their stuff in a way that pretty much prevents third party ‘Snap Stores’? Like, their backend being closed source and their software only accepting their own signatures?

      • Fizz@lemmy.nz
        link
        fedilink
        arrow-up
        4
        ·
        6 hours ago

        I dont know for sure so disregard what I say. but I remember reading that users could host their own snap repos but canonicals one was the only one at the moment. Everything about snap is open source except the webserver.

        • lengau@midwest.social
          link
          fedilink
          arrow-up
          2
          ·
          5 hours ago

          Yeah the API is open and there used to be an open store, but lack of interest ended up with the project shutting down. As it turns out people don’t like alternative stores nearly as much as they like the idea of alternative stores.

    • SwingingTheLamp@midwest.social
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      9 hours ago

      Has it? My complaints are: I have to use VPN software for work that replaces /etc/resolve.conf with a symlink to another location, one that sandboxed snaps can’t access. There’s no way to grant them access; the “slots” that you can connect are fixed and pre-defined. You can’t even configure the file path; it’s defined right in the source code. Not even as a #define, but the string literal “/etc/resolve.conf”. That seems like poor practice, but I guess they’re not going for portability.

      Also, I have /usr and /var on different media, chosen for suitability of purpose, and sized appropriately. Then, along comes snap, violating the File Hierarchy Standard by filling up /var with application software.

      Minor annoyances are the ~/snap folder, and all of the mounted loopback filesystems which make reading the mtab difficult.

  • MehBlah@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    3
    ·
    12 hours ago

    Like a bunch of old farts in a coffee shop arguing over which truck brand is better.

  • procapra@lemm.ee
    link
    fedilink
    arrow-up
    17
    arrow-down
    2
    ·
    14 hours ago

    If flatpak didn’t make me put the entirety of KDE onto my system (thats an exaggeration but you know what I mean) I’d gladly crown it king of the package managers.

    • rtxn@lemmy.worldM
      link
      fedilink
      arrow-up
      11
      ·
      10 hours ago

      I just want to point out the dependencies of Konsole (arguably a small and simple application in concept): glibc gcc-libs icu kbookmarks kcolorscheme kconfig kconfigwidgets kcoreaddons kcrash kdbusaddons kglobalaccel kguiaddons ki18n kiconthemes kio knewstuff knotifications knotifyconfig kparts kpty kservice ktextwidgets kwidgetsaddons kwindowsystem kxmlgui qt6-5compat qt6-base qt6-multimedia sh.

    • sensiblepuffin@lemmy.funami.tech
      link
      fedilink
      arrow-up
      18
      ·
      12 hours ago

      Plus make it hell on earth to a) access drives other than the one flatpak is installed on, b) interoperate with non-flatpak applications, and c) retain any amount of free space on my drives (exaggeration for effect).

      • JayDee@lemmy.sdf.org
        link
        fedilink
        arrow-up
        5
        ·
        9 hours ago

        Yeah, flatseal should come stock with flatpak IMO. You will have to configure many apps to get them to play nice with your system.

      • OsrsNeedsF2P@lemmy.ml
        link
        fedilink
        arrow-up
        6
        arrow-down
        1
        ·
        12 hours ago

        This is a “security” feature and I’m so tired of it. Same thing with Wayland, random crap doesn’t work sometimes

        • sensiblepuffin@lemmy.funami.tech
          link
          fedilink
          arrow-up
          17
          arrow-down
          1
          ·
          12 hours ago

          Wayland is trying to replace a standard that people have been saying is obsolete for a decade. I’ll give them a bit of leeway.

    • OsrsNeedsF2P@lemmy.ml
      link
      fedilink
      arrow-up
      14
      ·
      12 hours ago

      Psst … the first KDE app you installed via your package manager also put “the entirety of KDE” onto your system.

      • CarrotsHaveEars@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        8 hours ago

        Indeed. As much of how loved and popular KDE is, fuck it. I use the glorious XFCE. XFCE is beautiful too. Fuck, I’m not the maniac who would waste 2GB just for my DE to look beautiful.

  • jaybone@lemmy.zip
    link
    fedilink
    English
    arrow-up
    15
    ·
    15 hours ago

    Are there enough watermarks on this meme? At least we got reddit covered.

  • Admiral Patrick@dubvee.org
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    1
    ·
    20 hours ago

    Let the hate of the crowd wash over me, but I don’t even like Flatpak, and I’ve got love-hate (mostly hate) relationship with AppImage as well.

    Just give me a system package or a zipped tarball.

    In recent years, have had to just get used to needing to build most projects from source.

      • jj4211@lemmy.world
        link
        fedilink
        arrow-up
        6
        ·
        11 hours ago

        I’d say that complete lack of a single consistent way to manage updates.

        I really don’t feel having to micromanage each piece of software.

        • Samueru_sama@programming.dev
          link
          fedilink
          English
          arrow-up
          3
          ·
          7 hours ago

          AppImage is meant to be updated using the embedded zsync info the runtime, that is the user should never have to open the app to update it.

          The user needs to have something like AM, appimagelauncher or appimaged that is then able to parse the info and update the appimages using appimageupdatetool

          This method also provides delta updates, meaning it doesn’t download the entire app but only a diff, see this test with CPU-X where it downloaded 2.65 MiB to update the app:

          TLDR: https://github.com/ivan-hc/AM

      • Björn Tantau@swg-empire.de
        link
        fedilink
        arrow-up
        20
        ·
        20 hours ago

        For me it is the “Windowsy” feeling of downloading an executable from some website. I prefer having all my packages managed in one place.

        • sensiblepuffin@lemmy.funami.tech
          link
          fedilink
          arrow-up
          4
          ·
          12 hours ago

          Interesting you compare it to Windows, given how in OS X you literally just drag applications into your Applications folder to install them.

          • cecilkorik@lemmy.ca
            link
            fedilink
            English
            arrow-up
            7
            arrow-down
            1
            ·
            19 hours ago

            For simple “apps” it is fine, but my computer is not a phone and I don’t use it like one. I mostly don’t want simple apps that have their own little sandbox to play in.

            I want full-scale applications that are so big they have to use system libraries to keep their disk size down. I also don’t want them in a sandbox. I want them to have full access to the system to do everything they need to do, I want them to integrate with far-flung parts of the system and other applications too. I only use applications I trust and don’t want them constantly pestering me about configuring permissions and access in just the right ways and opening all the right doors and ports and directories to make them work, I trust them by installing them, they have permission, and the easier they make it to access everything I will inevitably be asking them to access, the happier I am.

            My practical concern with distribution methods like AppImage and Flatpak is that now I have to do a lot of extra thinking every time I’m installing anything. To pick how I’m going to install something, I have to solve the matrix of “what kind of distribution method do I prefer for this type of software” combined with “what distribution methods are available for this software” and “what versions are the available distribution methods for this software” and “what distribution method provides the best way for this software to get updates”.

            In the olden days, when the distro’s package manager was the only choice, all I had to care about was “is it available in my distro” and the decision tree was complete. I appreciate all the availability of choice that things like AppImage provide, but it doesn’t actually make it easier for me, it just makes it easier for the packager of the software. They’re doing less, but making more work for me, as a user. Distro packages are a lot of work for the maintainer precisely because they at least make an effort to solve many of these issues for the user. The value-add that maintainers provide is real.

            • Samueru_sama@programming.dev
              link
              fedilink
              English
              arrow-up
              4
              ·
              7 hours ago

              omg I cannot fucking believe that while I was typing this I just saw another distro package nonsense:

              There is this very good tool called soar which I use for static binaries. (It also has support for appimages but to be honest it is not as good as AM rn).

              Well we just got a complain that fastfetch is not displaying the package count of soar, which fastfetch is able to do.

              Turns out this is because the archlinux package is built without SQLITE3 which is needed for that feature to work 😫

              And what’s worse is that account registrations are disabled in the archlinux gitlab, so I have to jump thru some hoops to get a basic bug report filed…

            • Samueru_sama@programming.dev
              link
              fedilink
              English
              arrow-up
              3
              ·
              7 hours ago

              I want full-scale applications that are so big they have to use system libraries to keep their disk size down

              Linux is in such sad state that dynamic linking is abused to the point that it actually increases the storage usage. Just to name a few examples I know:

              most distros ship a full blown libLLVM.so, this library is a massive monolith used for a bunch of stuff, it is also used for compiling and here comes the issue, by default distros build this lib with support for the following targets:

              -- Targeting AArch64
              -- Targeting AMDGPU
              -- Targeting ARM
              -- Targeting AVR
              -- Targeting BPF
              -- Targeting Hexagon
              -- Targeting Lanai
              -- Targeting LoongArch
              -- Targeting Mips
              -- Targeting MSP430
              -- Targeting NVPTX
              -- Targeting PowerPC
              -- Targeting RISCV
              -- Targeting Sparc
              -- Targeting SystemZ
              -- Targeting VE
              -- Targeting WebAssembly
              -- Targeting X86
              -- Targeting XCore
              

              Gentoo used to offer you the option to limit the targets and make libLLVM.so much smaller, but now rust applications that link to llvm have issues with this with caused them to remove that feature…

              Another is libicudata, that’s a 30 MiB lib that all GTK applications end up linking to for nothing, because it is a dependency of libxml2, which distros override to build with icu support (by default this lib does not link to libicudata) and what’s more sad is that the depenency to libxml2 comes because of transitive dependency to libappstream, yes that appstream that I don’t even know why most applications would need to link to this.

              And then there is archlinux that for some reason builds libopus to be 5 MiB when most other distros have this lib <500 KiB

              Sure dynamic linking in the case of something like the coreutils, where you are going to have a bunch of small binaries makes sense, except you now have stuff like busybox which is a single static bin that acts as each of the different tools by checking the name of the symlink that launched it and it is very tiny at 1 MiB and it provides all your basic unix tools including a very good shell.

              Even Linus was surprised by how much dynamic linking is abused today: https://lore.kernel.org/lkml/CAHk-=whs8QZf3YnifdLv57+FhBi5_WeNTG1B-suOES=RcUSmQg@mail.gmail.com/

              To pick how I’m going to install something,

              https://github.com/ivan-hc/AM

              I have all these applications using 3.2 GIB of storage while the flatpak equivalent actually uses 14 GiB 💀: https://i.imgur.com/lvxjkTI.png

              flatpak is actually sold on the idea that shared dependencies are good, you have flatpak runtimes and different flatpaks can share, the problem here is that those runtimes are huge on their own, the gnome runtime is like 2.5 GiB which is very close to all those 57 applications I have as appimage and static binaries.

              but it doesn’t actually make it easier for me, it just makes it easier for the packager of the software

              Well I no longer have to worry about the following issue:

              • My application breaking because of a distro update, I actually now package kdeconnect as an appimage because a while ago it was broken for 2 months on archlinux. The only app I heavily rely from my distro now is distrobox.

              • I also get the latest updates and fixes as soon as upstream releases a new update, with distro packaging you are waiting a week at best to get updates. And I also heard some horror stories before from a dev where they were told that they had to wait to push an update for their distro package and the only way to speed it up was if it was a security fix.

              • And not only you have to make sure the app is available in your distro packages, you also have to make sure it is not abandoned, I had this issue with voidlinux when I discovered the deadbeef package was insanely out of date.

              • Another issue I have with distro packages in general is that everything needs elevated rights to be installed, I actually often hear this complains from linux newbies that they need to type sudo for everything and it doesn’t have to be this way, AM itself can be installed as appman which makes it able to work on your HOME with all its features. And you can take your HOME and drop it in any other distro and be ready to go as well.

            • MrQuallzin@lemmy.world
              link
              fedilink
              arrow-up
              6
              ·
              19 hours ago

              It doesn’t sound like they’re making more work for you. It sounds like you’re making more work for yourself, and it sounds exhausting.

            • notabot@lemm.ee
              link
              fedilink
              arrow-up
              0
              arrow-down
              1
              ·
              14 hours ago

              I couldn’t agree more. Occasionally I’ll use an appimage where something is not packaged for my distro version and I only need it temporarily.

              Maybe I’m just long in the tooth, but linux used to be a simple, quite elegant system, with different distros providing different focuses, whether they were trying to be windows clones, something that a business could bank on being there in ten years, or something for those who like to tinker. The common theme throughout was ‘the unix way’, each individual tool was simple, did one job, and did it well. Now we seem to be moving to a much more homogenous ecosystem of distros with tooling that tries to be everything all at once, and often, not very well.

            • Monstrosity@lemm.ee
              link
              fedilink
              English
              arrow-up
              0
              arrow-down
              1
              ·
              edit-2
              19 hours ago

              Most update themselves & flatpaks are the worst when you need them to work with your system (ie: scripts).

              So I guess your opinion is just wrong, sorry! (That’s a joke you guys)

              • Kusimulkku@lemm.ee
                link
                fedilink
                arrow-up
                2
                ·
                18 hours ago

                I despised the Windows way of everything having their own updater either running in the background or only alerting you when you want to use an app.

                AppImage to me feels like a big step backwards.

              • HunterLF@lemmy.zip
                link
                fedilink
                arrow-up
                0
                ·
                19 hours ago

                Damn, should have said that sooner, I see people don’t tolerate that kind of talking to others in here. Respect the community.

      • Admiral Patrick@dubvee.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        20 hours ago

        Just not a fan of container formats in general.

        I say that as a heavy user of Docker, but that’s a different use-case.

          • Admiral Patrick@dubvee.org
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            19 hours ago

            At least for appimage, it doesn’t create application launchers. And it’s 50/50 whether the icon in the window list works or not.

            I also build a lot of Docker images, and container formats throw a wrench in that if that’s the only way the application/utility is packaged. So I end up building from source.

            • klu9@lemmy.ca
              link
              fedilink
              English
              arrow-up
              0
              ·
              19 hours ago

              Personally, I use AM. Takes care of that and more.

              It is CLI and I’m GUI by nature, but AM is easy enough for me. Just yesterday I did a simple am -u and got the latest updated versions of qBittorrent, FreeTube, yt-dlp etc. (I.e. the kind of program that system packages are too out of date to work safely or even work at all.)

              There are other options like zap (CLI), Gear Lever (GUI) and just recently I believe the Nitrux distro came out with a complete AppImage software manager. (Checking it out, https://github.com/Nitrux/nx-software-center , it seems it pulls from AppImageHub.com, which unfortunately has largely been forgotten by developers, a lot of software is either out of date, unverifiable or completely absent. AM is much more up-to-date, pulling the latest AppImages mostly from official GitHub repos.)

  • cley_faye@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    16 hours ago

    A rusty bucket riddled with holes and the stick part of a shovel is better than snap for running software.

    • scintilla@lemm.ee
      link
      fedilink
      arrow-up
      6
      ·
      8 hours ago

      How the hell do you learn to use nix. I’m not a programer but figured out how to run gentoo just fine with the guide. nixOS feels like I’m in a mirror maze in the dark and the room is rotating.

      • kibiz0r@midwest.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        6 hours ago

        Well, Nix is a programming language, so there’s no getting around having to learn basic principles of coding.

        That said, I feel like coming into Nix with a lot of programming experience actually worked against me at first, because I made a lot of assumptions that weren’t true and basically had to “unlearn” certain things.

        The main things being:

        • Lazy evaluation is trippy as hell sometimes
        • The language truly does not allow for side-effects. Everything you might think is a side-effect is really executed from outside the language runtime itself
        • It might be more accurate to think of Nix as a database, where the keys are the parameters of what to build and the values are directories full of the built artifacts

        What really made it click for me was seeing how a derivation object is basically equivalent to a path. So if I do ${pkgs.foo}/bar”, that’s the exact absolute path (plus /bar) where Nix will end up storing the output of the pkgs.foo derivation. Even without actually building the derivation, you can know where it will end up.

        Anyway, the documentation is pretty shitty, so you basically have to scour every community resource you can find and read way more of it than it seems like you should have to. Discord/Matrix servers help a lot too. And learning to navigate the source code for nixpkgs.

        Also: Don’t start with NixOS, imo. Start with dumb throwaway stuff where you make a derivation that downloads a file and unzips it and runs a single command. Once you understand that, do something that requires understanding a bit of nixpkgs, like using overlays. Then you can use NixOS. Otherwise, there’s too much going on all at once.

        Edit:

        • Nix pills is good
        • Vimjoyer is amazing
  • 👍Maximum Derek👍@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    11
    ·
    19 hours ago

    A stab at my personal ranking: .deb > appimage > flatpack > curling a shell script

    I can’t help but love a .deb file (even when not via repo), I’ve almost exclusively used Debian and it derivatives since the late 90s. And snap isn’t on the list because it got stored in a loopback device I removed.

    • someacnt@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 hours ago

      Am I the only one who struggled extensively with .deb file with out-of-date dependencies? It seems the software dev needs to update the .deb file frequently, which they never do.

    • miguel@fedia.io
      link
      fedilink
      arrow-up
      5
      ·
      19 hours ago

      I just recently de-snapped yet another ubuntu system. Couldn’t agree more. I use debian standard for all of my stuff, and I agree with your ranking.

      • Damage@feddit.it
        link
        fedilink
        arrow-up
        2
        ·
        18 hours ago

        As someone who hasn’t used Ubuntu since the time they used to mail disks for free, may I ask why? Why not install another distro?

        • cley_faye@lemmy.world
          link
          fedilink
          arrow-up
          6
          ·
          16 hours ago

          Ubuntu support online (I mean, the size of the community) can be useful. And besides the snap and “ubuntu advantage” thing, they’re mostly a more up to date vanilla Debian, which is extremely convenient because, Debian.

          It’s obviously good for people used to Debian, but it’s also great for other, because of the regular updates. But in fairness with your point I’ve been thinking about moving to mint since it’s basically a de-snapped ubuntu.

            • cley_faye@lemmy.world
              link
              fedilink
              arrow-up
              4
              ·
              11 hours ago

              When I switched to Ubuntu, they just had more up to date packages, and with two releases a year (sort of), stayed up to date with other software, which is a good thing for a system I actually use. From then on, I just stayed on it, because I don’t reinstall my OS until something’s broken. I’ve been moving the same one for a decade now.

              If I had to install a new desktop system I’ll probably go with mint, for the same reason : more frequent software update.

              Note that this is all for desktop (and some specialized systems). Servers are all running debian, because stability is preferable and frequent software change is not what I want in these environments.

            • comfy@lemmy.ml
              link
              fedilink
              arrow-up
              2
              ·
              edit-2
              10 hours ago

              Not that user: My biggest problem with Debian was that packages were often so out of date (even sid). This was a big issue for the kinds of software I wanted to run, and also generally denied me useful newer features in most programs. Security and stability weren’t that device’s most important values.

            • miguel@fedia.io
              link
              fedilink
              arrow-up
              2
              ·
              10 hours ago

              I say this to be fair, since I’ve used Debian since almost the very beginning: Debian is a bit more complicated to set up.

              I generally find when people ask me for help, they’re either on Ubuntu or on Fedora (in which case I direct them to someone else for help). Sometimes they’re gamers or using something where Debian + tweaks is ideal, but often I just help them configure Debian, or just help them get their Ubuntu where they want it.

    • gigachad@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      ·
      19 hours ago

      As someone who is confused when he has to deal with a .deb file and always has to google what to do with it - what is the advantage of a .deb over let’s say a shell script?

      • wolfinthewoods@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 hours ago

        It might be different for other distros, but for me on MX Linux, I just click on the .deb and it opens a shell with a root prompt and installs the file automatically. Easy peasy.

      • cley_faye@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        16 hours ago

        If made correctly (which is hilariously easy), it’s a clean install and uninstall process, support some level of potential conflict regarding files that are shared with other packages/commands, support dependencies out of the box, and with minimal work can be made easy to update for the user (even automatically updates, depending on the user’s choices) by having an (again, very easy to setup for a dev) repository. With the added value of authenticity checks before updating.

        All this in a standardized way that requires no tinkering, compatibility stuff, etc, because all these checks are built-in.

        Note that some of this probably applies to other system package management solutions, it’s not exclusive to .deb.

      • Monstrosity@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        17 hours ago

        dpkg -i <nameofpackage.deb>

        Which can be read as: (Debpackage) -install <nameofpackage.deb>

        That’s it!

        Also, if you haven’t already, install tldr (apt install tldr), then you can ‘tldr deb’ (or any other command) to get a few examples of their most used functions.

      • 👍Maximum Derek👍@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        18 hours ago

        I never fully trust a shell script and usually end up reading any I have to use first, so I know what they do. And after so many years dpkg holds no mysteries for me and Discover will install .debs if I double click while in KDE.

        • everett@lemmy.ml
          link
          fedilink
          arrow-up
          3
          ·
          18 hours ago

          It’s worth knowing that .deb files can contain setup scripts that get run as root when installed, so you should trust them too.

          • 👍Maximum Derek👍@discuss.tchncs.de
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            6 hours ago

            Yeah. They all come with risks, but I psychologically struggle to run shell scripts unless I know what’s in them. And the same brain dysfunction makes my automatically distrust a script that doesn’t set pipefail.