I think it's personal preference of the developer. ie.if you need a certain function from a library, then a little extra initial dl time may be worth it. You can also trim prototype / scriptaculous down to include only the functions you are using, instead of the whole thing.
-=Randy On Oct 17, 2007, at 7:21 AM, "Steve Finkelstein" <[EMAIL PROTECTED]> wrote: > > So I'm trying to search through the previous threads, but I guess my > search skills are lacking their spinach this morning. > > Essentially, I was curious if you folks who're developing your web > applications for the iPhone are bothering loading libraries such as > prototype or jQuery into your iPhone specific pages. While these > libraries are fascinating to use for desktop applications, one might > hesitate loading that extra overhead onto a device that needs to > retrieve documents over the EDGE network. WiFi is not always > available, so I cannot use that to factor in whether the libraries are > worth sacrificing the user experience. > > My question is, are any of you using it and regretting it? Are you > optimization developers just sticking to core javascript in order to > obtain fastest page loads over the EDGE network? > > I did go to an iPhone developers conference recently and jQuery + > Prototype were mentioned briefly on their slides. Conversations did > not arise about them, and unfortunately, I was too pre-occupied to ask > such a pertinent question. > > Thank you again for any insight. > > - sf > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
