> You are literally putting forth arguments in favour of fixing the thread safety issue, and then conclude it’s not worth the effort. Yes. I do. These two conc

> You are literally putting forth arguments in favour of fixing the thread safety issue, and then conclude it’s not worth the effort. Yes. I do. These two concepts don't contradict each other. > No it’s not a performance problem. So we can make it thread safe, and the performance impact will be negligible Who said anything about performance being the problem, or a reason not to change it!? The problem is BACKWARDS COMPATIBILITY. The issue is that `getenv` returns a `*char` into the envvar array. Basically every application that uses this function relies on this fact. So we have: a) A potential issue that occurs only in very unusual circumstances, most of which will never occur in production code and on the odd chance that they do, they can easily be avoided. Documenting that well can help prevent time wasted in debugging. b) A fix that may prevent a) but breaks backwards compatibility promises, and would necessitate reworking god knows how many programs, the vast majority of which were never impacted by the issue in the first place. Of these 2 options, a) is just the better one. Yes, in an idea world, we could have pure, 100% bug free code, and spend an unlimited amount of time on fixing every last problem. That's not the world we live in however, and so a pragmatic approach is simply a necessity.