Comments by "Chaos Corner" (@chaos.corner) on "Linux Environment Variables Are Kind Of Weird" video.

  1. The correct answer is that getaddrinfo should be fixed or redefined as not thread safe. If not fixed, a thread safe implementation should be used either through local implementation or using another library (this is open source, after all). I'm not sure the logic of why getaddrinfo calls getenv but it might be worth looking into that too.
    15
  2. Because it's not envconst?
    4
  3. Yeah, if your libraries do stuff that breaks stuff, it's going to break stuff. That's always been the case.
    1