3 ms·
>and then thinking of next step is the exact opposite of "being cautious". I don’t think you fully grok the risk of code changes in some of these large legacy
by kortilla 7y ago
>and then thinking of next step is the exact opposite of "being cautious".
I don’t think you fully grok the risk of code changes in some of these large legacy systems. EOL with no security patches on a closed system that processes trusted inputs is nearly 0-risk.
- Havoc 7y ago>fully grok the risk Oh I get the risk. What I don't get is someone sitting on this for a decade and at EOL starting to wonder how this is gonna work. >nearly 0-risk That's cool to. I mean there are *nix servers with years of uptime that haven't seen a proper update since ever. All good (sorta). I coded in Python 2 last week - nothing against it. It's the bizarre "this decade long transition just snuck up on us" tone of the question that gets me.