I had to explain the same thing to an engineering team the other day. There was a push to switch from a "fast but ok" compression algorithm to a "faster and bet

I had to explain the same thing to an engineering team the other day. There was a push to switch from a "fast but ok" compression algorithm to a "faster and better" compression algorithm. This seemed like win-win, but I explained that: * The faster compression made a difference of about 100 milliseconds to a user experience lasting minutes. * The better compression made a different of about 1 second to most users. * The change of compression algorithm would take time away from engineering teams, and ultimately introduce bugs. So in the end it was sidelined until other fundamental changes (file format etc) made it able to be coat-tailed into production. Same story as yours: don't fix what ain't broke. Tallest working radio antenna in the world -> longest lying broken antenna in the world.