• FauxLiving@lemmy.world
    0·
    12 days ago

    Based on my years of community experience, whichever you pick is wrong and you’re a bad person for thinking that it was the right choice.

  • Cyberwolf@feddit.org
    0·
    12 days ago

    I think I just reached the point where my NixOS is configured exactly as I want, so now the system just works and works without me changing anything. 😭 I’m gonna have to start having sex since I can no longer justify it on the lack of time.

    • JGrffn@lemmy.world
      0·
      12 days ago

      Boring is good indeed. I’m running Bazzite on both my gaming desktop as well as my work laptop (webdev). The only reason I think about Bazzite at all is because I see it mentioned everywhere and feel the need to share my experience. Otherwise, it really is out of sight, out of mind.

      • horrorslice@lemmy.worldEnglish
        0·
        12 days ago

        Yup. I agree. Immutable distros save me from myself and endless tweaking. I have it on my gaming laptop and my gaming desktop. I’ll be throwing it on my wife’s gaming desktop soon enough.

        • rumschlumpel@feddit.org
          0·
          12 days ago

          I don’t have any experience with immutable distros, are they harder/impossible to tweak, or just easier?

          • horrorslice@lemmy.worldEnglish
            0·
            11 days ago

            The core files are read-only. You can layer new system applications, but it’s not as easy as just installing a package. Most things are handled via Flatpaks. So the base is solid and you can’t do much to really ruin the stability.

            There is a learning curve, as it’s different than normal distros.

            Here is a decent read up on it: https://www.linuxnest.com/what-is-an-immutable-distro

      • cally [he/they]@pawb.socialEnglish
        0·
        12 days ago

        It’s there to solve your “This is boring” issue without having to do all of the system configuration stuff manually*.

        I was able to package a nightly AppImage as if it were installed normally like an app, and I could reinstall the system if I wanted to, and it’d still be there. NixOS is the opposite of manual dependency resolution, it’s dependency heaven. You can have unstable and stable repositories side-by-side, living in a utopic egalitarian society. You can write a configuration file that does everything. You can do anything with NixOS. NixOS is the one true god, all hail NixOS—

        Ah, I see why you may not want to use it. Consider it though, it’s genuinely good and trying doesn’t hurt.

        I haven’t even told you about nix-comma or nix helper (nh) yet. May the, uh, flake be with you.

        *You do have to write the config files, though you can just adapt someone else’s configuration.

        • Cyberwolf@feddit.org
          0·
          12 days ago

          You can have unstable and stable repositories side-by-side, living in a utopic egalitarian society.

          The NixOS-communist intersectionality is something I never expected to come across, but it makes so much sense lmao. This is 100% true.

    • Bonje@lemmy.world
      0·
      12 days ago

      I adore the idea of nix. I fucking hate the syntax with a passion.

      oh use the .packages but only for this else use a flake and if you want dot files there is this other completely different thing with home manager but if you want this extra config customization or a custom system script then you need to make a derrivatio…

      its so damn exhausting.

      I just want a list of packages.

      That I can put in modules.

      And turn them on and off based on the computer I’m on.

      And if they are on they should use these dots.

      And not look like a spaghetti bowl made of curly braces sourced from json derulos left buttock.

      And the system should also have some additional sbctl hooks because we still have not figured out that dracut generated initramfs files don’t get purged from the database so I have to have a custom hook to not get error messages every time I paru ahahahAAHAHA…

      anyway dcli exists and is a fine middle ground.

  • Bluewing@lemmy.world
    0·
    10 days ago

    This is why you need to have 2 computers. One to run a boring distro that just works. And the other one for installing distros that you can ride for fun as it goes down in flames.

    The best of both worlds.

    • Pommes_für_dein_Balg@feddit.orgOP
      0·
      12 days ago

      Tried that, but my autism didn’t like it.
      The fact that YaST and the KDE settings had overlapping functionality, a GUI package manager frontend that shows you options you aren’t supposed to use in Tumbleweed, and it being the only modern distro that couldn’t install my printer-scanner-combo automatically drove me off.

      • insomniac_lemon@lemmy.cafeEnglish
        0·
        2 days ago

        For me, I didn’t like patterns (or the work-arounds). A shame because it (or now, maybe slowroll) might be closer to what I’m looking for, especially if the talk of smoke-testing is true. (I’ve also seen someone say that Zypper is slow)

        I like some of what I’ve seen with NixOS, though I see quite a few things that make it seem like not the answer either. And some of the things (like distrobox) seem like they probably add weight to updating as well (and/or clunkiness, if I have to manually do it).

        Also some of my issue is I’m still running a 1050Ti (and Arch putting the legacy drivers on the AUR, a bit of a pain for me… not sure if that has changed though), I know that’d likely be even worse on Nix as well.

        Ideally I’d like something that has an update system intended for slower internet. Something that can pull (/keep) slightly older dependencies when user-land stuff is a bit slow, or outright delay/reschedule possibly-broken (for any number of reasons) updates rather than wasting a user’s time and bandwidth. Guessing it doesn’t exist, though (or if it does, it has some other huge workflow flaw).

        Mentioning @LostWanderer@fedia.io because they’ve talked about Tumbleweed and Nix.

        • LostWanderer@fedia.io
          0·
          1 day ago

          I think Patterns are pretty rad (as you can customize what’s installed in the Graphical Installer and hit the ground running. It’s pretty easy to uninstall and make certain packages taboo. I think the one annoyance with them is that it tells you every time that it won’t install those taboo packages. Personally, I find zypper to be pretty zippy; there are times it can be slow if I am downloading huge things like games or updating my laptop at the same time.

          I think an update system intended for slower internet would be a challenging thing to make happen. As you’d have a lot of additional moving parts that would need to be balanced in a precise way or that house of cards would collapse quickly. Making a system either unresponsive or worse, broken. I feel it would be a workflow nightmare of a scale that would beggar belief and it would need constant attention from the maintainers…Something we’d probably not see in our lifetimes.

          I do agree with your Flatpak grievances, as that is a valid thing to be concerned about, especially since you have slow internet. I would love if Flatpaks could share a singular library of dependencies (based on the currently installed Flatpaks). This is why I am very careful to use a small amount of them as there are a few apps I can’t install through the package manager or RPMs. They are handy for this reason alone, but need a lot of refinement before being a better packaging solution.

          I’d love the concept of permacomputing to become a bigger thing…As that would mean longer support windows for hardware and operating systems that are highly efficient with the utilization of system resources. Not requiring users to constantly chase the latest upgrades every 10 or so years. I would love that gap to grow towards 30 or 40, systems that outlive their users before you need to upgrade hardware. Operating Systems that don’t have super fucking flashy stuff added all the time, just sensible refinements that aren’t going to tax a user’s hardware. You’d have to opt in for the flashy stuff, but the ability to make a choice and not have it forced on you is such a wonderful idea. This is why I like Linux so much, there is a lot of choice that can fit a person’s use case!

  • KindaABigDyl@programming.dev
    0·
    12 days ago

    For me, I always keep coming back to Arch tbh

    Sometimes I get fed up with managing a whole system and once in a blue moon bricking my system on an update, but the alternatives are always worse, and with btrfs now, I don’t have to worry about the latter problem.

    Nix was the closest to pulling me away. A centralized config? Beautiful. Static package store without dependency conflicts? Beautiful. Immutable applications? The WORST idea we’ve ever had as a community. For instance, imo, VS Code extensions are fundamentally incompatible with Nix. I spent weeks trying to get it to work doing multiple different things to try and hope it would work. It can’t. VS Code just has to be mutable.

    Anyway so I’m back to arch and have been for over a year since I tried Nix (and before that Fedora which has its own issues). Before that I had been on Arch for 4 years.

    I think I’ll stay now. It’s really the best option out there. In my mind, Arch is Linux, i.e. it’s how an OS should be built for the Linux kernel and the FOSS ecosystem, and it won’t ever be beat