Sure, but in the case where you upgrade python and it affects python packages it would affect global packages and a venv in the same way.
bio
Sure, but in the case where you upgrade python and it affects python packages it would affect global packages and a venv in the same way.
upgrading your base image won’t affect your python packages
Surely if upgrading python will affect your global python packages it will also affect your venv python packages?
you can use multi stage builds to create drastically smaller final images
This can also be done without using venv’s, you just need to copy them to the location where global packages are installed.
He is a front end dev/engineer and he mainly talks about the UI (which is his expertise).
Here are their repos: https://github.com/zen-browser
and here is a video from Theo on youtube looking into zen browser: https://www.youtube.com/watch?v=tKM2N4TQHQY
I don’t think they have anything to do with each other, it looks like prefix.dev uses conda packages.
Yeah it is, eventually they want UV to have feature parity with rye and rye will basically just be a pointer to UV
Early on uv was only trying to replace pip. This latest update is a big step towards becoming a poetry (and pyenv/pipx) replacement too.
It worked for me with just: virtualisation.libvirtd.enable = true;
in the configuration.nix
.
Stable channels provide conservative updates for fixing bugs and security vulnerabilities, but do not receive major updates after initial release.
If you want up to date packages then use the unstable channel.
Nix has the most unique packages and the most up to date packages of any Linux software repository. It has substantially more fresh packages than Arch or Alpine (which you say does a better job in a separate comment).
Yeah I agree, I am sure they are missing some obscure stuff. But in practise it has everything that I use and there has been no need for me to touch flatpak/appimage/snap
yep, I mean a GUI based software centre
NixOS:
I think it will easily be the number 1 distro if/when they can :
One thing I haven’t seen mentioned is that not moving between mouse and keyboard so much reduces the risk of getting an RSI. So even if it didn’t make you faster it would still probably be worth it to find a keyboard based workflow.
I use Helix and would suggest you try it (at least to start off with) as it is easier to learn than vim and does not require plugins or a complex config. To answer your question I will go from the less to more advanced/complex:
x
then d
to select a line (pressing N times will select N lines) and delete it (delete will also copy to the clipboard)p
to paste in a newg
then d
when on a function/class usage.g
then r
.
to select the entire files contentss
to searchv
then g
then l
to select the rest of the linespace
+y
to copy to the system clipboard.There is actually a helix community on programming.dev: helix@programming.dev
deleted by creator
How often do you run nixos-rebuild --switch?
If you don’t run it regularly then you will likely be waiting for a few different packages to get updates. To fix this you can configure auto upgrades:https://nixos.wiki/wiki/Automatic_system_upgrades
I have definitely found it challenging at times to do even simple things. I think it does get easier over time.
I really hope the new user experience will improve. Once the issues with flakes are fixed and they are no longer experimental I would expect flakes to replace the other ways of doing things. This will hopefully make the documentation more concise/focused/better. It might also mean more people start using nix/flakes which will surface more of these problems to be fixed.
I think people need to decide if the benefits they are getting are worth the challenges. I personally really like the reproducibility and the massive amount of packages available from one place. On other distros I have used things have ended up breaking eventually and I have had to re-install things and search for fixes. But on NixOs things keep working.
“I’m playing both sides, so that I always come out on top”
If you do multi stage builds (example here) it is slightly easier to use venvs.
If you use the global environment you need to hardcode the path to global packages. This path can change when base images are upgraded.