*with the indispensable help and guidance of the conda-forge core team!
Yesterday, I seemingly became 'patient zero' of a bug in conda-forge's C compiler toolchain with the new macOS 26, where executables it compiled would immediately crash. Thankfully, the conda-forge core team were on hand to find the one-line patch needed to fix the problem, and guide me through the process of contributing the fix! I wrote a blog post describing the problem and how we fixed it on the same day it was found.
The takeaway for me is the evident power of free and open-source software — and especially of community-owned software distributions like conda-forge — that if somebody (or some big company) breaks your software, you can go and fix it yourself (/with the help of the conda-forge core team, who keep conda-forge running, often on a volunteer basis!), right down to the fundamental tools like the C compiler!
*with the indispensable help and guidance of the conda-forge core team!
Yesterday, I seemingly became 'patient zero' of a bug in conda-forge's C compiler toolchain with the new macOS 26, where executables it compiled would immediately crash. Thankfully, the conda-forge core team were on hand to find the one-line patch needed to fix the problem, and guide me through the process of contributing the fix! I wrote a blog post describing the problem and how we fixed it on the same day it was found.
The takeaway for me is the evident power of free and open-source software — and especially of community-owned software distributions like conda-forge — that if somebody (or some big company) breaks your software, you can go and fix it yourself (/with the help of the conda-forge core team, who keep conda-forge running, often on a volunteer basis!), right down to the fundamental tools like the C compiler!