[Building Sakai] Javascript Libraries

[Charles Severance]

I agree that we want to "keep up" as browsers evolve - but sadly JQuery is playing this game that if you want to work with the latest in the browsers you are force-fed their deprecate-and-pitch quickly strategy.

What JQuery needs to do is commit to compatibility libraries - they have become the Browser's operating system and are not yet behaving responsibly IMHO.

I agree that it is bad to freeze too much - but in a way, defining a master JQuery version and then changing that version for us is like changing Java versions.  It needs to be done thoughtfully and carefully and with plenty of conversation and notice - but we do have to move forward albeit slowly.

/Chuck

On Jan 13, 2014, at 10:32 AM, Aaron Zeckoski <azeckoski at unicon.net> wrote:

> If you (or anyone really) are doing anything to up-convert in the
> jQuery 1 series now or soon then you should be targeting 1.10 and not
> 1.9. The http://jquery.com/upgrade-guide/1.9/ and migrate plugin both
> still apply but you get the newest and best fixes in 1.10 (and
> eventually 1.11 etc.)
> 
> That said, there is no way in the world I would ever be using a
> non-specific version of jQuery as a tool developer, core developer, or
> developer in general. I don't think anyone else should either.
> Unfortunately it is a reality of how jQuery is run and versioned and
> sorta a lesson in minor vs major versioning and API stability.
> 
> I don't think it is worth trying to have a "portal" or "centralized"
> version of jQuery that is non-specific. Freezing the version seems OK
> but not at a 1.9 version and depends on what kinds of fixes the jQuery
> guys come up with to deal with the ever changing browsers.
> 
> -AZ

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140113/7d1d0b6f/attachment.html