It can be "very, very old" in its context. If a new release comes out every year, support duration is 5 years and you're 2 years past EOL, I'd agree that the software can be called "very, very old".
And that's where things go off the rails. A release that is only supported for five years is a hobby project.
The kind of software projects that make the world go round continue past the lives of their original authors and can easily span decades. 5 years is just enough for the original shake-out.
A finished software product that gets regular updates is old by the time it turns 7, I'd agree on that.
Dependencies on libraries is a different story, there's only so many ways you can implement a functionality, and some of these happen to be decades old!
Youden|5 years ago
jacquesm|5 years ago
The kind of software projects that make the world go round continue past the lives of their original authors and can easily span decades. 5 years is just enough for the original shake-out.
diarrhea|5 years ago
Dependencies on libraries is a different story, there's only so many ways you can implement a functionality, and some of these happen to be decades old!
unknown|5 years ago
[deleted]