Hey all, thought this might be of interest to some here.

Wrote about why I moved from NixOS to Ubuntu after using it for several months on my daily driver. Suspect that this take is likely to be kind of controversial and court claims of skill issues, which might even be true.

Let me know what you think.

  • IndustryStandard@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 year ago

    More serious than this is the rare occasions Nix packages conflict with each other. While Nix separates dependencies, it doesn’t separate them as absolutely as a full container system like Docker. Therefore it is possible, albeit unlikely, to end up with conflicts between versions of installed libraries.

    Never tried it but thanks for dispelling the hype. What a meme OS.

  • Deckweiss@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 year ago

    tldr:

    • fucking with configs for hours regularly
    • pip & venv doesn’t work on nixos
    • DE broke when installed new DM
    • not much community support
    • mortalic@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I didn’t realize pip and venv didn’t work… that’s a pretty big deal breaker for a lot of people, myself included.

      • frozencow@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        pip and venv are working, but packages that require compiling or ship binaries by itself usually won’t work out of the box. They depend on gcc or libopenssl to be globally available: the whole gist of Nix not doing 😅

        I’ve found devenv.sh to be most convenient way to handle such projects. You can define the dependencies for a project. It has explicit python/venv/requirements.txt/poetry support. It works for NixOS, but also other distros and MacOS. Very convenient to share and lock development tools and libraries across a team.