I have asked, unsubscribed 5 times from this group and I continue to get emails.
Any emails sent to me from this group are spam and they will be reported as so. On 5/4/10 4:58 PM, "Andy Fuchs" <[email protected]> wrote: > What's your problem? > > a. > > > On 05.05.10 01:43, "Brian Willis" <[email protected]> wrote: > >> SPAM >> >> >> On 5/4/10 4:44 PM, "Andy Fuchs" <[email protected]> wrote: >> >>> On 04.05.10 21:45, "Scott Kallen" <[email protected]> wrote: >>> >>>> Hey, folks. >>> >>> Hi Scott, >>> >>>> We're trying to get moving forward with a web-based iPhone app and I >>>> still don't feel I have a great handle on the plusses and minuses of >>>> the various JS frameworks. We did a "Web 2.0" project a way back and >>>> used SPRY over jQuery, much to our pain (because Macromedia/Adobe >>>> seemed to support it at the time.) >>>> >>>> In that vein, I would love to get the opinions of users new and old of >>>> the various frameworks available. Our primary questions are these: >>>> >>>> 1) How mature is the framework? >>> >>> Mature... >>> >>>> 2) How is the project vitality? (How quickly are things fixed and new >>>> features added?) >>> >>> Depends. In my experience there are no real show-stopper bugs and things >>> improve quite fast. >>> >>>> 3) How big is the team working on the framework? >>> >>> Dunno... but from the checkins and discussions it seems quite huge. >>> >>>> 4) What's the track record of this team? (Has the team (or >>>> individual) completed and deployed any other products?) >>> >>> I don't know what this question is about? If people completed and released a >>> bunch of iPint and iFart frameworks, would this make things better or worse? >>> ;-) >>> >>>> 5) How responsive is the team to (reasonably intelligent) questions >>>> about the framework? >>> >>> I think, this depends on the intelligence of the questions, and the amount >>> of bucks you're willing to sponsor. >>> >>>> 6) How up-to-date is the documentation kept? >>> >>> Documentation is extremely good and detailed (and current). >>> >>>> Feature set is obviously a factor but that's much easier to figure >>>> out. Ease-of-use is also a factor, but a secondary one. We'll put in >>>> a little extra work for the right backbone. >>> >>> One important thing for me (in webapps) is the size/functionality ratio, >>> since users tend to use the stuff on their way to the airport or whatever - >>> and in situations where online connections may be weak. IMHO jQuery offers a >>> great size/functionality ratio here. But even more important is the fact, >>> that it saves huge amounts of developing power (read: time), if it comes to >>> DOM-manipulation and parsing. >>> >>>> Obviously, some might not know answers to all of the above, however, >>>> all suggestions are welcome. >>> >>> Your questions are valid and understandable. But: look in the mirror: >>> - Are you willing to contribute, or just suck the code? >>> - Are you willing to discuss, or just ask? >>> >>> IMHO the experience with an open framework is always as good as the will to >>> contribute is. >>> >>> jQuery performs great so far, if that was the overall question. >>> >>> best >>> >>> andy >>> >>> >>> >>> >>> >> >> > > > -- 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.
