On Thu, Jan 17, 2013 at 10:19 AM, gloesch <gloe...@taximagic.com> wrote: > Thanks! Yeah, I agree that AQuery doesn't seem near as powerful as jQuery. I > do know that this library uses reflection in certain instances, particularly > for callbacks in network calls. This doesn't seem to cause issues.... though > I just started using it. >
It won't hurt you until you use it a little more. Reflective code runs pretty slow compared to statically compiled code. > I liked in particular the lack of boilerplate code for asynchronous calls > (http://code.google.com/p/android-query/wiki/AsyncAPI). It seems like a > really nice wrapper to what I'd assume to be AsyncTask. Probably, or another kind of thread pool based facility. FYI there are good frontends to AsyncTask, and I'm not sure how much control this really gives you over AsyncTask's parameters. (Since Java uses templates for parametric polymorphism versus being a duck typed language, you're not going to get the succinctness of JQuery with a Java library, because you'd have to infer type parameters to the template..) kris -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en