Got it backwards!
There is no reason to do this. In fact, there is every reason to do the opposite. Chrome should be using libcurl as its networking library. I reworked a substantially sized application to use libcurl instead of its own protocol implementations, and was able to shed tens of thousands of LoC. And at the same time, the networking stack got more reliable (because more people have tested it) and we didn't have to maintain any of that stuff anymore.
Biting the hand that feeds IT
