59
Why I Left NixOS for Ubuntu (fd93.me)
submitted 2 years ago by to c/programming@programming.dev
43 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 22 points 2 years ago (2 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 9 points 2 years ago (1 child)

    I'm not a Nix user, but doesn't Nix make both pip and venv obsolete in a way? Nix is a package manager (which could be used to package anything including Python packages/modules) and also allows you to create environments that include only certain packages of certain versions.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 14 points 2 years ago (1 child)

    Sounds good in theory, until you want to install scikit-image or other Python libraries which need complex builds.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 2 years 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.

  • permalink
  • fedilink
  • source
  • parent