I think the other side of this is the fetishization of "if it isn't broken don't fix it" and computing conservatism a la the famous Dropbox/rsync comment. An eq

I think the other side of this is the fetishization of "if it isn't broken don't fix it" and computing conservatism a la the famous Dropbox/rsync comment. An equally valid inquiry is to ask "why should we not replace it", which can lead to some valid and correct thoughts. At the end of the day, greybeards are going to retire and new generations are not going to want to deal with code bases built around technology and decisions that were made in the 1990s.