pixi is the youngest tool in this quest. These rules let you adopt it as a credible long-term bet.
pixi is for projects that need conda-forge. If your project is pure Python with no compiled deps, plain uv is simpler. pixi shines when you need PyTorch + CUDA, GDAL, ffmpeg, R packages, or other heavy binary deps that conda-forge solves and PyPI doesn't.
Always commit pixi.lock. Same iron rule as every other lockfile in this quest. pixi.lock is text-based, fairly stable, and IS your reproducibility.
Use pixi run, not pixi shell, for one-off commands. Saves the activation overhead and is closer to how you'd write it in a Makefile or CI script.
Use the task runner instead of Makefile. Tasks in pixi.toml have depends_on, environment selection, cross-platform args. They're more capable than basic Make targets and they live next to your deps.
Watch the project — it's still moving fast. pixi has a release every 1-2 weeks and breaking changes happen. Pin the pixi version with [pixi] in pixi.toml if you want stability across team members.
Migrate from conda incrementally. 'pixi init --import environment.yml' gives you a working pixi.toml on day one. Iterate on tasks, features, and environments as your project's complexity demands.