On 2025-05-10 00:29:33, Jacob Bachmeyer wrote: > > Programs either no longer compile with a newer compiler or (worse) > compile but with different semantics. I *think* Rust has only had the > first of those problems, but have not followed the issue closely enough > to be sure. Python infamously had the latter problem with the > Python2->Python3 transition, but that at least had a major version bump > associated with it.
The ABI is also unstable, so you can't upgrade rust libraries without recompiling the entire system. This is a minor headache. But to work around these issue, all rust projects bundle specific (old) versions of their dependencies. This leads to rust package versions being meaningless (because who cares, because everyone pins a version that works) and is a much bigger headache. While not a problem with the language per se, it does make most rust software incompatible with the usual linux-distro-style system management, and ensures that one day rust will have its own log4j vulnerability. It's also less portable than C which may matter to people on an autoconf list, though again this is not a fundamental language issue.
