This may be the unpopular opinion, but I would never use this. It adds to much complexity in my opinion. To many things that can break. Sure it gives you a lot of stuff that makes things quicker to implement. Plus you have to abide by their design and now how you think it should work. And frankly that doesn't sit well with me.
Not unpopular at all. I've been considering this precise thought myself. So far haven't bailed yet, but still looking into it.
Concerns are that once I make my own, I will make the same mistakes, and in the end it would have been fruitless.
AFNetworking is one of those libraries that is if I were to remake it, I'd make similar mistakes and end up hating what I made.
Comments
This may be the unpopular opinion, but I would never use this. It adds to much complexity in my opinion. To many things that can break. Sure it gives you a lot of stuff that makes things quicker to implement. Plus you have to abide by their design and now how you think it should work. And frankly that doesn't sit well with me.
Not unpopular at all. I've been considering this precise thought myself. So far haven't bailed yet, but still looking into it.
Concerns are that once I make my own, I will make the same mistakes, and in the end it would have been fruitless. AFNetworking is one of those libraries that is if I were to remake it, I'd make similar mistakes and end up hating what I made.
What mistakes do you think AFNetworking has made?
Incredibly bloated, massive interface files, too many coupled classes.