[geeklog-devel] AJAX and Javascript Libraries - request for comments

[Vincent Furia]

Just a warning, while there are some nice advantages to using Google to load
these libraries (speed, and only forcing users to have one copy of the
libraries cached are the big ones), there are some considerations that need
to be made...

1. Geeklog would not control when updated versions get loaded (including
security fixes and bug upgrades).
2. If Google is down (or the part of google that hosts the libraries), AJAX
won't work on your site.
3. While I doubt Google would go away, there is chance they could stop
supporting this service.

On the "third" hand, the first and third points are mitigated by this
statement:
"Google works directly with the key stake holders for each library effort
and accepts the latest stable versions as they are released. Once we host a
release of a given library, we are committed to hosting that release
indefinitely."

-Vinny

On Tue, Feb 3, 2009 at 1:48 PM, cordiste <cordiste at free.fr> wrote:

> Today I saw a google way :
>
> The AJAX Libraries API is a content distribution network and loading
> architecture for the most popular, open source JavaScript libraries.
> By using the Google AJAX API Loader's google.load() method, your
> application has high speed, globaly available access to a growing list
> of the most popular, open source JavaScript libraries including:
>
>    * jQuery
>    * jQuery UI
>    * Prototype
>    * script.aculo.us
>    * MooTools
>    * Dojo
>    * SWFObject
>    * Yahoo! User Interface Library (YUI)
>
> http://code.google.com/intl/fr/apis/ajaxlibs/
>
> ::Ben
>
>
> 2009/2/3 Dirk Haun <dirk at haun-online.de>:
> >>there is clearly a need for a JS library to made it easier
> >>to code the functions and UI components to handle and enrich the user
> >>interface.
> >
> > So, after only 4 posts I'm already counting recommendations for 6
> > different JS libraries :-)
> >
> > Which is why my original idea was to set up a GSoC project "Find us an
> > AJAX library" where we pre-select some candidates and then the student
> > would implement some tasks with each of them to get a better idea what's
> > working and what isn't.
> >
> > Okay, so maybe a GSoC project would be overkill. Still, I'd like to see
> > us base a decision on something a bit more substantial than "I'm
> > familiar with it".
> >
> > For example, how do these libraries compare on things like
> > - security
> > - footprint / overhead / load times
> > - ease of use / learning curve
> >
> > bye, Dirk
> >
> >
> > --
> > http://www.haun-online.de/
> > http://spam.tinyweb.net/
> >
> > _______________________________________________
> > geeklog-devel mailing list
> > geeklog-devel at lists.geeklog.net
> > http://eight.pairlist.net/mailman/listinfo/geeklog-devel
> >
> >
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20090203/ab1231c7/attachment.html>