I make iOS and Android applications for a living.
It is ridiculous to have to create a service to make a few HTTP calls.
For that, Android/Java provides various threading classes so that you can keep multi-threaded code nice and neat.
With iOS, out of the box, you get NSURL and its family.
You have to setup callbacks in your class and you have to keep track of your http calls per class by using things like action=whatever. What a pain.
ASIHTTPRequest makes things much easier.
Ugh, this just makes me mad. Why would people listen to shitty developers?
Why are you spreading this ignorance?
Objective-C is a giant paint, with opaque types.
Having to remember what class you've put into a dict can get messy.
I have to work with both frameworks every day, and Android is the better framework BY FAR.
Care to rebuke?
BTW, read hackbod's comment. She's an Android engineer. This guy is flat out wrong and failed to read documentation.
She puts it much nicer than I can.
I make iOS and Android applications for a living. It is ridiculous to have to create a service to make a few HTTP calls. For that, Android/Java provides various threading classes so that you can keep multi-threaded code nice and neat.
With iOS, out of the box, you get NSURL and its family. You have to setup callbacks in your class and you have to keep track of your http calls per class by using things like action=whatever. What a pain. ASIHTTPRequest makes things much easier.
Ugh, this just makes me mad. Why would people listen to shitty developers? Why are you spreading this ignorance?
Objective-C is a giant paint, with opaque types. Having to remember what class you've put into a dict can get messy.
I have to work with both frameworks every day, and Android is the better framework BY FAR.