mamba

I'm glad I clicked through bc I thought the article was about Mamba, the package manager I associate with Python (similar to conda). https://github.com/mamba-org/mamba

As far as the solver is concerned, there should be no difference as it has been streamed. But I personally can’t see a reason to go back, as mamba is supposed to be a drop in replacement of conda. I default to use mamba and switch to conda only when necessary. There are some cases mamba can’t handle correctly, such as the case where you want to roll back to an earlier revision: https://github.com/mamba-org/mamba/issues/803

> Please consider consolidating python dependency management instead of fragmenting it: https://github.com/mamba-org/mamba Mamba doesn't even interact with the official python packing ecosystem... It is purely a conda replacement and conda packaging is not Python packaging (it's a more fundamental fragmentation than choosing a particular tool). So weird choice to not fragment Python dependency management. If you depend on both conda and standard Python packaging (e.g. PyPI.org) you can use Pixi: https://github.com/prefix-dev/pixi?tab=readme-ov-file#pixi-p.... Pixi attempts to bridge the conda world and the Python package world, so it's possible to rely more deeply on standards based packaging but still use conda tooling when you need it.

Please consider consolidating python dependency management instead of fragmenting it: https://github.com/mamba-org/mamba In other words, bring the thinking here. Whether it's new thinking, or decade old thinking, it's well time to converge. We've had decades of trying it like Heinz catsup varieties. Worth trying more wood behind fewer arrows.

Completely - I assumed it was an implementation of https://github.com/mamba-org/mamba I also assumed that "a pure NumPy implementation" meant that it was built purely with numpy, which it isn't smh

Very annoying namespace conflict since a package called "mamba" (faster reimplementation of the python conda package manager) already existed for awhile before this architecture was even dreamed up. https://github.com/mamba-org/mamba Beyond that, I'll care about an alternative to transformers when it shows superior performance with an open source 7b-34b model compared to transformer model competitors. So far this has not happened yet

For conda there is mamba [0], a drop-in replacement that's really fast. By the way, the creator of mamba started his own company at https://prefix.dev/ They want to essentially leverage the conda(-forge) infrastructure to build a new cross-platform, cross-language, cargo-like package manager: pixi [0] https://github.com/mamba-org/mamba

Mamba is also the name of a package management system, similar to Conda. Just to make it a little extra confusing :) https://github.com/mamba-org/mamba

>"everyone" seems to know Mamba. I never heard of Mamba Only the "everybody who knows what mamba is" are the ones upvoting and commenting. Think of all the people who ignore it. For me, Mamba is the faster version of Conda [1], and that's why I clicked on the article. https://github.com/mamba-org/mamba

Have you ever tried mamba[0]? It's much, much faster than conda for me. 0: https://github.com/mamba-org/mamba

Great writeup. Minor comment about the portion of the post mentioning Conda being glacially slow: Mamba [1] is a much better drop-in replacement written in C++. Not only is it significantly faster, but error messages are much more sane and helpful. That being said, I do agree that Pkg.jl is much more sleek and modern than Conda/Mamba. [1]: https://github.com/mamba-org/mamba