Update download.jsx to mention pixi

[phreed]

While pixi-build is still under active development it should be mentioned as a conda-forge installer.

[netlify]

✅ Deploy Preview for conda-forge-previews ready!

Name	Link
🔨 Latest commit	13a6d2a
🔍 Latest deploy log	https://app.netlify.com/sites/conda-forge-previews/deploys/67b8c200625e980008d74cd0
😎 Deploy Preview	https://deploy-preview-2465--conda-forge-previews.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 60 Accessibility: 96 Best Practices: 100 SEO: 89 PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[synapticarbors]

I'm wondering if mentioning pixi-build here makes sense? I can see the case for including pixi, as it is analogous to conda/mamba in terms of installing and managing environments. On the other hand, I think pixi-build would cause confusion for users who I'm guessing are coming to the page to get an environment manager (and conda-build is not mentioned here).

[phreed]

I'm wondering if mentioning pixi-build here makes sense?

I think pixi build should be mentioned, but definitely separated from the installer part.

[isuruf]

There is one canonical installer which is miniforge.

pixi, micromamba, conda, mamba are tools which can use conda-forge packages. This distinction is not made here. If you are adding pixi here, we should add micromamba, conda, mamba as well.

[phreed]

Why is miniforge considered to be the canonical installer?
Is it because, originally, conda had dependencies? like pip, python, etc and miniforge took care of installing all that?
Then mamba, and micromamba got added in later?

Given that micromamba and pixi do not have these dependencies miniforge seems like it would be more confusing than helpful. But maybe that is just me.

I have no problem adding in descriptions for micromamba, conda, mamba as well.

[isuruf]

Why is miniforge considered to be the canonical installer?

Because that's the only installer produced by conda-forge. Others are related and influenced by conda-forge, but not fully part of conda-forge.

[phreed]

Why is miniforge considered to be the canonical installer?

Because that's the only installer produced by conda-forge. Others are related and influenced by conda-forge, but not fully part of conda-forge.

So, the significance is that when doing things which are blessed by conda-forge the expectation is that miniforge will be used? I am thinking of something like processing a feedstock.

What has me confused is that miniforge is canonical but the things it installs are not canonical.