Comparison with mamba
#227
Labels
documentation::explanation
related to higher-level clarification (understanding-oriented)
severity::4
low; functionality is inconvenient
source::anaconda
created by members of Anaconda, Inc.
type::feature
request for a new feature or capability
Milestone
Comments
jezdez
added
documentation::explanation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
What is the idea?
mambahas been a very appealing alternative forcondausers who struggled with longer and longer solve times. Many users have then started to routinely replaceconda installwithmamba installin their workflow. However, I believe it has never really been explained thatmambais not just a fastercondabut comes with many differences. Users probably often don't care about these differences, when things go wrong though they end up in a much larger problem space.If I understand correctly
conda-libmamba-solverprovides adaptations on top of the mamba solver to get it closer in behavior to classic solver, implementing various heuristics. While it seems there still remains differences between the classic solver and this one (https://conda.github.io/conda-libmamba-solver/libmamba-vs-classic/), as a conda/mamba user I'd expect runningconda installwith this solver to get a solve closer to the one I'd get with runningmamba install. So if that is true, I wish the documentation would clearly highlight thatconda-libmamba-solveris a better alternative thanmambaasmambais not just a fasterconda.My motivation for this request is that as an open-source maintainer my interest is in having users that use one tool, or multiple tools that implement the same behavior, as debugging why solving an environment got library version X instead of Y with tool Z isn't super fun :)
Why is this needed?
No response
What should happen?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: