AJAX Libraries API: Speed up your Ajax apps with Google’s infrastructure
1–10 of 20 posts
Re: AJAX Libraries API: Speed up your Ajax apps with Google’s infrastructure
#2This is really cool, but I'm not sure I'd use it because of the plugin issue. Usually, I don't just use JQuery - I use JQuery, plus a few JQuery plugins, plus JQuery UI, plus some custom JavaScript files that are built off this. To deploy them, I concatenate them all together in dependency order, minify the whole thing, and GZip it. That saves HTTP requests, and multiple files with the same coding standards tend to compress very well. (JQuery + Dimensions + Dropshadow + Corner = 20504 bytes when compressed together, vs. 21919 bytes when compressed separately.)
It looks like with this, I'd need to request JQuery off Google's infrastructure and then all the other stuff off my own, so it's multiple requests where one used to do, and you don't get the benefit of compressing them together.
Re: AJAX Libraries API: Speed up your Ajax apps with Google’s infrastructure
#3Excellent. With pipelining browsers this will speed things up even on the first hit
Re: AJAX Libraries API: Speed up your Ajax apps with Google’s infrastructure
#4It's a neat idea, but I can't imagine using it. Do you really, really trust Google with your business? What happens when google decides to "fix" something in one of those frameworks that the upstream developers disagree with? Even worse, what happens when your app is irreconcilably broken because of something that happened at Google? Worse still, what happens when your app somehow becomes reliant on Google's version of the framework(s), and you don't realize it until it would be too expensive to unhook yourself from Google?
Re: AJAX Libraries API: Speed up your Ajax apps with Google’s infrastructure
#5This is really cool, but I'm not sure I'd use it because of the plugin issue. Usually, I don't just use JQuery - I use JQuery, plus a few JQuery plugins, plus JQuery UI, plus some custom JavaScript files that are built off this. To deploy them, I concatenate them all together in dependency order, minify the whole thing, and GZip it. That saves HTTP requests, and multiple files with the same coding standards tend to c…
While I think you have some good points, the difference between 20504 and 21919 bytes is completely meaningless.
Re: AJAX Libraries API: Speed up your Ajax apps with Google’s infrastructure
#6This is really cool, but I'm not sure I'd use it because of the plugin issue. Usually, I don't just use JQuery - I use JQuery, plus a few JQuery plugins, plus JQuery UI, plus some custom JavaScript files that are built off this. To deploy them, I concatenate them all together in dependency order, minify the whole thing, and GZip it. That saves HTTP requests, and multiple files with the same coding standards tend to c…
While I think you have some good points, the difference between 20504 and 21919 bytes is completely meaningless.
It's brings it down to one request _and_ it reduces the filesize. Requests are relatively slow, you want as few as reasonable possible.
Re: AJAX Libraries API: Speed up your Ajax apps with Google’s infrastructure
#7edit Nevermind, nothing to see here edit
In the video they say that they used many of Steve Souders' techniques to speed up the deliver of the files since most web servers aren't properly optimized out of the box
Looks like Google missed the part in Souders' High Performance Web Site where he talked about using ETag to speed up sites. :P
curl -I http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js
HTTP/1.1 200 OK
Last-Modified: Mon, 26 May 2008 18:45:05 GMT
Content-Type: application/x-javascript
Expires: Wed, 27 May 2009 17:39:22 GMT
Date: Tue, 27 May 2008 17:39:22 GMT
Cache-Control: public, max-age=31536000
Content-Length: 55740
Server: GFE/1.3Re: AJAX Libraries API: Speed up your Ajax apps with Google’s infrastructure
#8It's a neat idea, but I can't imagine using it. Do you really, really trust Google with your business? What happens when google decides to "fix" something in one of those frameworks that the upstream developers disagree with? Even worse, what happens when your app is irreconcilably broken because of something that happened at Google? Worse still, what happens when your app somehow becomes reliant on Google's version…
There's nothing new about depending on external parties - if your site hosts ads (or uses an external stats service) you're already running code hosted elsewhere, so you should probably be comfortable linking through to Google (I trust them a lot more than most ad networks). The question is always "do I trust this provider not to screw me over" - Google's developer network stuff HAS to be trustworthy or they'll lose the hearts and minds they've been cultivating overnight.
As for your app becoming reliant on Google's version of the framework, you can always download the JS file they've been serving and host it yourself. You can't get locked in that way.
Re: AJAX Libraries API: Speed up your Ajax apps with Google’s infrastructure
#9edit Nevermind, nothing to see here edit In the video they say that they used many of Steve Souders' techniques to speed up the deliver of the files since most web servers aren't properly optimized out of the box Looks like Google missed the part in Souders' High Performance Web Site where he talked about using ETag to speed up sites. :P curl -I http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js HTTP/1.1…
I don't think you need an ETag if you're serving a Last-Modified.
Re: AJAX Libraries API: Speed up your Ajax apps with Google’s infrastructure
#10It's a neat idea, but I can't imagine using it. Do you really, really trust Google with your business? What happens when google decides to "fix" something in one of those frameworks that the upstream developers disagree with? Even worse, what happens when your app is irreconcilably broken because of something that happened at Google? Worse still, what happens when your app somehow becomes reliant on Google's version…
There's nothing new about depending on external parties - if your site hosts ads (or uses an external stats service) you're already running code hosted elsewhere, so you should probably be comfortable linking through to Google (I trust them a lot more than most ad networks). The question is always "do I trust this provider not to screw me over" - Google's developer network stuff HAS to be trustworthy or they'll lose…
As for your app becoming reliant on Google's version of the framework, you can always download the JS file they've been serving and host it yourself. You can't get locked in that way.
This misses the point. I'm not concerned about where the file comes from. If breakage occurs with regard to where the download comes from, a few customers get annoyed while you fix it (or even better, you implemented caching and customers never know the difference). That's a normal and expected maintenance issue that you plan for.
What I'm really talking about is the content of the file. If Google fixes bugs or adds features and you don't realize it until your app has become dependent on Google-specific changes, it's not an easy thing to fix. This is a different problem than getting screwed over by ad providers.