The problem is that neither the original thread, nor the threads here (which seem to be quite heavy on Google commenters) answers the question 'why?'. I think

The problem is that neither the original thread, nor the threads here (which seem to be quite heavy on Google commenters) answers the question 'why?'. I think this wouldn't have caused nearly as much commotion as it does now, if the original post explained the technical reasons for starting a new libc. What problems do existing implementations have? How could a new libc address these issues? Instead, this has an air of (regardless whether this is true): we are going to write a new libc for completely opaque company-driven reasons, and either you accept it or you we will make it happen anyway.