Google AJAX Libraries API

[timb]

I was just reading this blog post (http://googleajaxsearchapi.blogspot.com/2008/05/speed-up-access-to-your-favorite.html). Here's a quote about what this is all about:

What exactly is the AJAX Libraries API?

We have worked with a subset of the most popular JavaScript frameworks to host their work on the Google infrastructure. The AJAX Libraries API then becomes a content distribution network and loading architecture for these libraries.

We realize that there are a huge number of useful libraries out there, but we wanted to start small with the program, which has us starting with:

* jQuery
* prototype
* script.aculo.us
* MooTools
* dojo


We work with the key stake holders for these libraries to make sure that the latest stable versions of their work get into our system as they are released. Once we host a release of a given library, we are committed to hosting that release indefinitely.

Has there been any talk about getting ExtJS in this program? I think this is a very good idea and I would really like to see this.

Regards,
Tim

[thejoker101]

And would any of the licensing issues currently going on prevent this from happening? I'd love to see Ext go on the list of those, but with all the controversy and misunderstandings coming from the license change, I don't know if that would happen anytime soon.

[ben.tremblay]

I was just reading this blog post (http://googleajaxsearchapi.blogspot.com/2008/05/speed-up-access-to-your-favorite.html). Has there been any talk about getting ExtJS in this program? I think this is a very good idea and I would really like to see this.

The list should look like this:
* jQuery
* prototype
* script.aculo.us
* MooTools
* dojo
* ExtJS

This indicates to me that the google geeks aren't up to speed on what's happening here ... which is just plain wrong. Getting onto that list would maybe be a great way of introducing them to this project.

Expedite!

[hbstone]

This indicates to me that the google geeks aren't up to speed on what's happening here ...

Possible, but Google? They're not known for being behind the times. Besides, with Ext GWT up and running surely SOMEone at Google has at least heard of Ext by now.

They are probably up to speed, but (as thejoker wonders above) they may not want to include it until the licensing dust settles. They'd be "allowed" to host the library, since they're not making modifications and even if they did, distributing the source IS their functionality, so they'd be complying with GPLv3.

Just conjecture, of course, but as the licensing issues calm down I bet Ext will show up on their list. I think it's a cool idea, especially with the google.load() feature and wildcard versioning.

[antimatter15]

I've been using CacheFile.net for the same purpose (yes, it has Ext). But Ext isn't really that much of a javascript library, as half of the download is all the CSS/Images that come with it.

[mystix]

But Ext isn't really that much of a javascript library, as half of the download is all the CSS/Images that come with it.


wouldn't that encourage the use of a CDN like google's / cachefiles?

p.s. without the (Ext) library, what good would all the css/images that come with it be? :-?

[Zyclops]

Given the size of the full extjs library + it's resources having extjs hosted on a cdn would be great.

[deanoj]

Just read the blog post myself and I think Ext would be an excellent addition.

You have my vote.

[tof]

This would indeed be a good news, I've been disapointed when I saw that extjs was not in the list :/

[thedave]

Maybe Ext isn't in the program because the google guys still have that ext-yui thing in mind. Yahoo and Google don't mix very well these times.... (YUI isn't in the list as well ;) )

[Lobos]

correct me if i am wrong, but this could be due to the licensing, ie those other frameworks have a more permissive licensing scheme (LGPL, BSD,etc) - too many gray areas in the gpl v3 for google to risk hosting ext, they would be "distributing" it os they would have to make all sorts of nasty rules for users like "no using non-gplv3 extentions" with it, etc, etc

[thejoker101]

Maybe Ext isn't in the program because the google guys still have that ext-yui thing in mind. Yahoo and Google don't mix very well these times.... (YUI isn't in the list as well ;) )
Well, Yahoo! does have their own hosting for the YUI library.

[richardtallent]

I asked (http://www.tallent.us/blog/?p=44) for Google to do this last year, I'm glad someone over there decided to do it.

I was disappointed not to see Ext JS on the list, and I hope the developers open a dialog with them to get on that list ASAP.

Offering to host merely *host* GPL-licensed code (i.e., not using it in their own apps) would not put Google in any dangerous position. The responsibility for license compliance always rests with the programmer *calling* the code.

[OutpostMM]

too many gray areas in the gpl v3 for google to risk hosting ext, they would be "distributing" it os they would have to make all sorts of nasty rules for users like "no using non-gplv3 extentions" with it, etc, etc
What???

Correct me if I'm wrong, but it's not Google's responsibility to make sure that people are using GPL code in a compliant way. It's the exact same issue with Windows trying to police media files, it's not Microsoft's responsibility to make sure that users are legally entitled to play a given piece of media, it's the user's responsibility to do that. Google doesn't have to make any allowance for any license that already permits them to host the files. That's like saying Sourceforge is in legal trouble for distributing GPL code without policing everyone who downloads it to make sure they are compliant.

Christ.

[Lobos]

yeah well i am not sure, but if the page you output has ext (from google) mixed in proprietory non gpl code from your own server what happens? hmm i guess the onus falls to the user here anyway (ie the users fault if they are mixing the code)... so idk

[jack.slocum]

Ext JS will be up on Google API in the near future. :)

[Lobos]

Ext JS will be up on Google API in the near future. :)

Nice one, while you are here do you have any more information on how the "Open Source License Exception for Extensions" will work? There are a few posts toward the end of the sticky thread that could do with your notice and feedback.

1. I would like to know what happens with extensions if I buy a commercial license - can I use them with my commercially licensed version of Ext?

2. Do you, Jack, Perceive the act of Extjs libraries being transferred to the client browser in a normal page view as being "distribution" and therefore an act for distributing software as per the definition of the gpl?

Thanks.

[damien]

I think it will not get on the list because of the licensing issues.

[FlexIDX]

why is it that non of the license issues / real questions get a response? Jack?>?????

[tof]

There are no licensing issues... ExtJS is GPL.

[timb]

Ext JS will be up on Google API in the near future. :)

I'm happy to hear that! Keep up the great work.

Tim

[mcurrey]

Glad to hear it, Jack. Thank you.

[stever]

Ext JS will be up on Google API in the near future. :)

Excellent news! Their CDN network is just too fast to ever compete with, and with the browser blocking on css and js loads, this can make a big difference.

Now only if they would do svn revisions... Or maybe Ext should push updates out more often, as having the CND available (and all our sites using a common cache) would be too hard to resist, and therefore having fixes up and running would be extremely important. Right now, it is not an issue as we roll our own. But when we don't...

[SeaSharp2]

Ext JS will be up on Google API in the near future. :)
Truly significant news, thanks Jack. Just think, Google's tops class CDN infrastructure is going to locate the ExtJS libraries only 30ms or so away from a majority of client browsers.

I am a little curious as to how the dual licence nature of ExtJS will map onto this Google hosted resource?

[Clay]

Ext JS will be up on Google API in the near future. :)

Jack, now that 6+ weeks have passed since your comment, can you define "near future"? It would be great to have the Ext library available on Google, but at this rate holding one's breath doesn't seem advisable.

Can you give another update?

Thanks!

[jheid]

Jack, now that 6+ weeks have passed since your comment, can you define "near future"? It would be great to have the Ext library available on Google, but at this rate holding one's breath doesn't seem advisable.

Can you give another update?

Thanks!

+1

[justokman]

Jack, now that 6+ weeks have passed since your comment, can you define "near future"? It would be great to have the Ext library available on Google, but at this rate holding one's breath doesn't seem advisable.

Can you give another update?

Thanks!

Any progress here?

[danh2000]

Polite Bump - is there any news on this?

From previous posts it sounded like a done deal, so I check every week or so, but still no Ext.

:(

Update:
Maybe anyone else who's interested could leave a request comment here:

http://code.google.com/p/google-ajax-apis/issues/detail?id=50

[Frank]

I second this request.

[jack.slocum]

No news yet guys. I'm not sure what the hold up is. :(

[antimatter15]

Come on everyone! Star it! The more stars it has, then the more this will be considered! We *only* have 12 now!

http://code.google.com/p/google-ajax-apis/issues/detail?id=50

[jonhobbs]

Starred.

[Frank]

Visited this page again, and Starred it.

[AlexRichardson]

Starred antimatter's link in post 31. You should too!

[antimatter15]

We need more!!

STAR IT!
http://code.google.com/p/google-ajax-apis/issues/detail?id=50

[DocSavage]

Did you heard any word from Google on the hold-up, Jack? It seems like they're going to do it because the status is "Accepted"...

I suggest people star the issue but refrain from "+1" comments:
http://code.google.com/p/google-ajax-apis/issues/detail?id=50

[justheatingup]

Can also try this in the meantime.

http://cachefile.net/

[nfinity]

starred it!

[mrileyaz]

Google has posted their response:


For now this will be a no-fix due to licensing issues. All libraries that we host on the Google AJAX Libraries API are offered free of charge with very liberal licenses. EXT, however, requires a fee for users wishing to use it commercially. We like to keep the libraries consistent so that we don't put our users in a dangerous situation where they might be liable without knowing it.

Status: WontFix

http://code.google.com/p/google-ajax-apis/issues/detail?id=50#c44

[jack.slocum]

Google has posted their response:


For now this will be a no-fix due to licensing issues. All libraries that we host on the Google AJAX Libraries API are offered free of charge with very liberal licenses. EXT, however, requires a fee for users wishing to use it commercially. We like to keep the libraries consistent so that we don't put our users in a dangerous situation where they might be liable without knowing it.

Status: WontFix

http://code.google.com/p/google-ajax-apis/issues/detail?id=50#c44

This is contrary to discussions we have had with them. I will check into it and find out if that is accurate.

[Chris503]

I guess Lobos was right in his post that he stated he does not think they would include it because of the license mess.

I am wondering if the GPL license change will ever die? I mean how many months ago did you change the license and the effects / comments / lack of support are still poping up on a daily basis.

[DocSavage]

The other possibility is using Amazon's new CDN:
http://aws.amazon.com/cloudfront/

It would be great if Ext JS provides one url for Extjs download since there'd be a lot of bandwidth savings via browser-side caching. Not sure if there's a way to split costs with those who want to use a centralized delivery url.

[jack.slocum]

The other possibility is using Amazon's new CDN:
http://aws.amazon.com/cloudfront/

It would be great if Ext JS provides one url for Extjs download since there'd be a lot of bandwidth savings via browser-side caching. Not sure if there's a way to split costs with those who want to use a centralized delivery url.

http://extjs.com/blog/2008/11/18/ext-cdn-custom-builds-compression-and-fast-performance/

The latest download version is available on there as well.

Google hosting the library didn't work out. It wasn't because of the GPL license, they wouldn't have hosted the older license either. Their latest reply to us (which was a change from the original) was that they couldn't do it because we offer commercial licenses and they didn't want to put anybody using their service in a position where they would need a commercial license without their knowledge. That makes perfect sense and we understand their position.

[DocSavage]

Thanks, Jack. Missed that great cache news.