Yes, but I don't understand this comment. Were you mislead by the title into thinking it was a visceral urgent article about concurrency that included a vision of nuclear holocaust?

"10 reasons not to use C for multithreading"

Not the OP, but I personally expected it to be a metaphor, and to colorfully describe a perpetually-impending disaster re: widely-used multithreaded applications, similar to the "horrors" of IPv4 exhaustion or Y2K-class bugs.

Also, this "article" is not an individual item of clothing or part of a legal constitution, it is a piece of writing.