Personally I haven’t. While Linux is imperfect, choosing the right distro makes the rest of the experience straightforward. And with it’s whole complexity, I find Linux more user friendly than Windows. Even driver issues, broken shadow file ownership and KDE specifics only made me more confident about my choice to use Linux after I solved everything.

OQB @pixeldaemon@sh.itjust.works

  • a14o@feddit.org
    0·
    3 months ago

    Give NixOS another look. It’s no problem to run a declarative system as a base, and plain old dotfiles on top if you want, especially for user stuff. Not sure what you mean by “non-packaged executables” exactly, but I don’t see how NixOS would give you a disadvantage here. Heoric works fine as a Steam alterntative.

    • insomniac_lemon@lemmy.cafeEnglish
      0·
      3 months ago

      and plain old dotfiles on top if you want

      I’m not the type to put my dotfiles in git, though. A lot of things I just plan on starting fresh and configuring in-session.

      Not sure what you mean by “non-packaged executables”

      Pre-compiled, non-system binaries.Typically, stuff downloaded from GoG and itch without a client (also the odd thing like BrogueCE). I don’t know if this is always an issue, but it is for anything that uses dynamic linking (checking with ldd is a thing, though can be misleading with runner scripts).

      Heroic works fine

      I’ve never been interested in the Epic store even for free games. I’m sure there are 10 ways to “solve” this each with their own benefits/drawbacks, but I feel like this is a philosophy issue that creates more problems than it solves for me. And this is without the ability to create static binaries (out of the box) like I’d get with void-linux musl.

      That, and seeing talk about how great Nix is but also people having trouble later on too (major updates? bleeding edge woes?).

      • a14o@feddit.org
        0·
        3 months ago

        I’m not the type to put my dotfiles in git, though.

        That’s what I’m saying, you don’t have to! Just install the package (like neovim or whatever) through NixOS and it will use your ad-hoc dotfiles like it would on any other distro. For a lot of stuff you can make use of declarative NixOS options (programs.neovim = { ... };), but you don’t have to, except for really basic system stuff like networking I guess.

        Pre-compiled, non-system binaries.

        Gotcha. There’s several ways do do this on NixOS (steam-run works like a charm!), but I’ll concede that there’s an extra step involved here that you don’t have to do on other distros.

        That, and seeing talk about how great Nix is but also people having trouble later on too (major updates? bleeding edge woes?).

        There’s a learning curve for sure, but I haven’t looked back or experienced any major issues (where I hadn’t shot myself in the foot) since 22.11.

        • insomniac_lemon@lemmy.cafeEnglish
          0·
          3 months ago

          you don’t have to! Just install the package
          and it will use your ad-hoc dotfiles like it would on any other distro

          And changes will last on reboot, y’know with the whole immutable thing?