• iopq@lemmy.world
    108·
    7 months ago

    Joke’s on you, I don’t understand Nix and I’m a NixOS package maintainer

      • iopq@lemmy.world
        17·
        7 months ago
        while code_is_working != true {
    response = post(matrix_channel, [code, error_code]);
    [code_is_working, error_code] = run(response);
}
      • bruhduh@lemmy.world
        10·
        7 months ago

        The secret is attitude, “fuck it we ball” attitude and method of “fuck around and find out” works just fine

    • S. G. Tallentyre@lemmy.today
      1·
      7 months ago

      Lol…

      I mean, fair enough; also, your use case is entirely unlike that of someone who just uses NixOS normally, I would imagine. It’s really not like using NixOS requires a deep understanding of the language itself, or at least that’s never been my experience with it, and I’ve been daily driving it for well over a year at this point. As long as I know enough to keep maintaining the same /etc/nixos/configuration.nix I have now indefinitely, that’s as deep of an “understanding” of the language as I will ever need, personally. I’m well aware that there are a lot of things I could be doing if I knew how to, and frankly, I’ll probably never learn how to do those things because I’ll probably never have to. NixOS is by far the single easiest distro I’ve ever used, if only because everything’s always reproducible and because nothing ever breaks.

      • iopq@lemmy.world
        4·
        7 months ago

        No, it’s just I need niche proxy software so I maintain one package. The other package is bugged (wrong paths on nix), so I maintain a fork and a NUR package

        It’s not by choice!

  • Lunya \ she/it@iusearchlinux.fyi
    721·
    7 months ago

    this post implies that you download debs from the internet instead of using your distro’s package manager

    also last I checked apt hasn’t stopped being a cli over the years

    • rickyrigatoni@lemm.ee
      8·
      7 months ago

      This meme reeks of someone who’s only used linux for a week and has no clue what he’s talking about.

    • lil@lemy.lol
      5·
      7 months ago

      When I was a beginner and used Linux Mint, I downloaded deb files, and even rpm files that I converted to deb, because I didn’t know what package manager means

    • Waffelson@lemmy.worldOP
      32·
      7 months ago

      I didn’t actually mean that you install deb packages from the internet, I mean debian based distros, I just don’t know the acronym for it.

      and AFAIK mx linux and LMDE have programs with a GUI for installing packages, and I added debian because it has a gui installer and I don’t know a good third debian based distro

  • jabjoe@feddit.ukEnglish
    18·
    7 months ago

    All power users, of all distros, use the CLI. It’s what unites us!

    I used the CLI a lot when I was on Windows and RISCOS before that.

  • countessssmeltdown@lemmy.world
    9·
    7 months ago

    I switched to Gentoo but use the Nix package manager, helps if I wanna test out some software before committing to the compile. it’s been great.

  • Diabolo96@lemmy.dbzer0.com
    113·
    7 months ago

    I just want to install the latest version of an app without downloading half an OS worth of dependencies. AppImage had me dreaming of this day but the project seems like it’s dying, if not dead already.

    • jack@monero.town
      5·
      7 months ago

      Didn’t appimage bundle all the dependencies inside it? That leads to way more taken disk space cuz of duplicate libs

      • Diabolo96@lemmy.dbzer0.com
        21·
        7 months ago

        I know this, but it’s still way lighter than flatpak. (the required app depencies size <<< whatever the hell flatpak downloads)

        An app image that weighs a few hundred megabytes ( it’s often less) becomes several gigabytes as a flatpak. I can download more than a dozen of appimages and it still would weigh as much as a single flatpak. I think it’s just that my use case require me to have a handful lightweight apps in their latest version and the rest can be managed by the OS.

        • jack@monero.town
          21·
          7 months ago

          Yes, the first flatpak is big cause you have to download the runtime (most common dependencies you will probably need anyways in the future). The majority of other flatpaks you will download will use the runtime you’ve already downloaded so those flatpaks will be lighter than the appimage variant

          • uis@lemm.ee
            24·
            7 months ago

            Solution to too many package managers: two more package managers

    • renzev@lemmy.worldEnglish
      51·
      7 months ago

      Flatpak nowadays feels like the spiritual successor to appimage. All the dependencies are containerized, and uninstalling an app doesn’t leave behind a residue of automatically created files on your system… at least in theory. All of these benefits are kind of negated if an app has full disk read/write permission.

      Appimage is kind of silly in my opinion. Appimage is just “portable application” (i.e. when an app gets shipped as a folder containing the executable, .so dependencies, and resources), but crammed into a disk image for some reason.

      • Diabolo96@lemmy.dbzer0.com
        42·
        7 months ago

        I was referring to flatpak when I said ‘half an OS worth of dependencies’. I have an extremely shitty and unstable internet, so downloading like 5gb for a simple app isn’t worth it. Even if my internet wasn’t as horrible, Flatpak is only worth it when you want to install dozens of big app and not when you want to install 2-3 apps, the heaviest being a 100mb or so as a .deb.

    • force@lemmy.world
      3·
      7 months ago

      i installed nobara and while everything was simple to set up, the nobara installer doesn’t recognize the ssd i flashed it on. going great