On Thu, 5 Aug 2021 at 21:49, Nick Hilliard <[email protected]> wrote: > It has the appearance of a feature which is kept alive because some > customer with a huge spend demands it in general-deployment release > trains (this is idle speculation and may be completely wrong btw).
More precisely, who (which employee) should be doing this, there is no ROI for pushing such a change, but there is a (tiny) possibility of blowback, in a company that is not exactly a stranger to layoffs. I don't think there are a lot of rewards for employees for fixing old lingering software problems, if any, *especially* in IOS. It's different if a specific BU is responsible for the code, but generic code from decades ago, the BU responsible for the code path today probably handles a million other things, some of them presumably do actually make money. What is right or technically correct is not always the priority. lukas _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
