> Just because it's been in use for a long time doesn't mean it's any good. Not conclusively, but I would argue that on average, code that is still in producti

> Just because it's been in use for a long time doesn't mean it's any good. Not conclusively, but I would argue that on average, code that is still in production after 28 years is going to provide a higher ROI over its lifetime than code written yesterday. In other words, the age of the code doesn't prove conclusively that it is either good or bad, but higher age is an INDICATION (as in correlation) of higher quality (at least for the time it was written). > We have plenty of problems with this system, Had you argued based on this, instead of the age, I would not have objected. > It's fine as a data transfer protocol, but it's terrible as a real-time communication interface. Again, had you specified that ftp/sftp was used for real time communication, I would not have objected. (It would have been fine for the 90's though, and might still be in use if it was completely stable.)