It's unfortunate that some platforms got dropped, but OTOH all these platforms seem to be 30 years old, niche, and discontinued by their original manufacturers.<p>If someone has antique computer that still works, that's great, but they shouldn't expect to have the <i>latest</i> software for it.
If you are using open source packages in a corporate setting you really should be
a) pinning versions
b) maintaining secure, internal mirrors instead of always pulling from Github etc.
That would prevent breaking your builds without being intentional about it, regardless of what changes upstream introduces.
There is a lot of "right side of history" / "get with the program" smugness coming from the Rust camp, this bug report and other discussions. Claims of improved security are used as an ultimate, unbeatable-by-definition, trump card.<p>This might prove right eventually - or might very well end up just like Java, for which similar claims were made. The smugness around Java was moderated a bit by the more corportey image of it, but the gist was quite similar nonetheless. Let's just say openly: the smugness is using up a lot of natural goodwill, and generating its own pushback. As there's no widely acknowledged "equal competitor" to Rust (why?), something feels "off" about the whole situation.
pyca/cryptography replaced C code with Rust code without bumping the major semver. This broke people's CI because it removed support for certain platforms which Rust barely supports or doesn't support at all. People are arguing over this change in the github comments, but the problem from my perspective is just with semver. The maintainers didn't do semver right.<p>Edit: the maintainers didn't do semver right because the maintainers didn't do semver
I’m not discounting the pains that some people are going through because of this change, but this response [1] in the issue says<p><i>> The new Rust code adds exactly 0 (zero) runtime packages to Cryptography. Rust, Cargo, pyo3, its dependencies, and setuptools_rust are build-time dependencies only.</i><p>Aren’t there tools available to build this on a supported platform and integrate the binaries in the systems in use? It is a bit convoluted, but seems like a solution at least for some (?) cases <i>at additional cost</i>.<p>[1]: <a href="https://github.com/pyca/cryptography/issues/5771#issuecomment-775028182" rel="nofollow">https://github.com/pyca/cryptography/issues/5771#issuecommen...</a>