I typically use PullToRefresh from https://github.com/leah/PullToRefresh instead of EGOTableViewPullRefresh. It positions itself as a superclass that handles all of the logic, rather than an external object that handles the delegate methods (as EGO does).

Obligatory plug for Resty: https://github.com/lukeredpath/LRResty ;)

How is AFNetworking easier than ASIHTTPRequest?

Simple block-based API, significantly less lines of code to accomplish the same tasks, and smaller, more understandable codebase that uses Foundation classes (e.g. NSURLRequest, NSURLResponse, etc.), rather than re-inventing the wheel

And though I don't have the exact numbers, AFNetworking is really fast, maybe 2-3x over ASI in average cases, from my experience and what other users report.

Take a look at the examples in the README and compare that to how you'd do the same in ASI.

doesn't ASI also use blocks? its syntax is very similar. but i didn't know about that it's much faster than ASI, thanks for that

This is awesome. Thanks for the tip.