On Sep 2, 2009, at 5:43 AM, Andrea Giammarchi wrote: > I think the best approach is to understand runtime what the browser > can do and what it cannot then call right pieces of the puzzle in > order to create the "perfect library". > > This will mean a sort of nightmare for each created ticket, but if > we are talking about performances, I have to insist I do not want > Opera 9 problems in "my jQuery for Firefox"
Isn't this essentially what jQuery does now? There could be an advantage to only going down those separate branches once, but as John said earlier in this thread, if the data supports that approach, it can be done at that point. > So, at the end of the day, what seems to be that simple to do, > requires a lot of work, a lot of tests to understand if it is worth, > and a deep analysis about side-effects, best approach, server load, > file serving strategy, method serving strategy, etc etc Indeed. Which is why it's a little silly to consider *how* to do it without first making sure *why* we're doing it is based on solid data. -- dz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
