3 ms·
I’ve never liked the “code rot” euphemism. Code doesn’t rot. What happens is platforms change out from under your code by platform vendors who no longer give a
by ryandrake 3y ago
I’ve never liked the “code rot” euphemism. Code doesn’t rot. What happens is platforms change out from under your code by platform vendors who no longer give a shit about backwards compatibility.
If you take a piece of application software, tar it up including its dependencies, you should be able to untar it 15 years later and it should compile and run. If it doesn’t, it’s not your fault as a developer—it’s the fault of everything else that changed and broke that previously working code.
If vendors took compatibility seriously, we wouldn’t have “code rot”.
- bdzr 3y agoI'm not sure what a better term is, but I think the problem will exist anyway. 15 years of backwards compatibility from software that's often written by volunteers is unreasonable to say the least.
- Falkon1313 3y ago>15 years of backwards compatibility [...] is unreasonable to say the least As a Windows user, it's sad that so many people think that way nowadays. I've encountered one DOS program from the early 90s that doesn't run anymore because it used its own custom memory management which newer systems don't allow, but that one was later re-released in an updated version that still works today. And there were one or two late-90s Windows programs that no longer run either because they have 16-bit components or depended on some then-standard now long-gone libraries to be on the system, but those run in a VM. Other than that, there is plenty of software dating back to the 90s, some to the 80s, that mostly still works fine. It doesn't need constant maintenance and updates. It worked about 30 years ago and still works today and should still work tomorrow. You'll find even older legacy code in major organizations that's still chugging along. That's hard to find in modern software. Now everyone always has to have the latest thing and it has to be updated almost every single day just to keep a massive chain of transitive dependencies from collapsing out from under it. I guess that's why people get rude and ask whether a project is 'dead' even though patches have been released for it multiple times within the last 10 years.