One of the reasons why I hate the over-use of third party libraries is that, while in theory it’s “the more eyeballs the better the code”, in practice none of us who use a third party library ever bother to trace bugs into the third party library. It’s because we think that third party library (especially one that has been around for a long time) is somehow “bug free”–when, as we all know, “too many cooks spoil the broth”.
(That is, we’ve seen in practice the more people who work on a software project in a corporate setting, the more likely there are bugs in the source kit, as different developers with different levels of aptitude work on the same source kit to varying results, often unchecked by his peers as most software projects are just too big for everyone to understand. So why is this different with third party libraries?)
In my case I managed to trace down a bug.
Let’s put it this way:
If, in your source kit, you have something like this:
#pragma clang diagnostic ignored "-Warc-retain-cycles"
You have a really bad memory leak bug which affects Every. Single. Fucking. App. that uses your code.
Now I’d forgive this if we’re talking about a small project and the person working on it wasn’t all that established in the community.
But this is a big honking library which is used by a lot of companies, where there are tutorials floating around on sites like NSHipster and Ray Wenderlich, and is often the very first library everyone wants to include that may engage in any sort of networking operations.
The good news is that 3.0 of AFNetworking did away with the problem.
The bad news is that 2.0 of AFNetworking has the problem in spades.