Correct me if I’m wrong, but Mamba appears to require Conda during its installation process. Why is it the case given that Mamba is a re-implementation?
By the way, Mamba’s integration with fish seems second-class, and it’s annoying that I must use conda activate foo instead of mamba activate foo.
conda activate foo
mamba activate foo
Mamba is a work-in-progress reimplementation. So it falls back to Conda for parts that haven’t been redone.
There’s a just-Mamba version called micromamba that is a self-contained single-file executable, but e.g. it doesn’t yet support pip package installs from environment.yml and is mostly just intended for bootstrapping environments in CI or Docker, not as a day-to-day tool for development.