Your Pages Will Load Faster With Rails
engineyard.com
Your Pages Will Load Faster With Rails
1–10 of 35 posts
Re: Your Pages Will Load Faster With Rails
#2This isn't just specific to Rails.
-Use Far-Future Expires
-GZip Components
-Split Components Across Domains
Re: Your Pages Will Load Faster With Rails
#3Wycats is a great guy and contributes a ton to the Ruby community, but I have to say...there's really not much here that's new or insightful.
Set your headers, gzip content, and split assets across domains, yes, but - "Your pages will load faster with Rails"? Somehow the headline doesn't seem appropriate.
Re: Your Pages Will Load Faster With Rails
#4I'd say download Firebug, YSlow, and Google's PageSpeed and let that be your guide, as these suggestions are helpful, but just the tip of the iceberg.
A YSlow feature that is new (at least to me) is its JavaScript tab. It's not related to performance exactly, but it will run your JS through jslint, minify, beautify it (if it's in a gnarly style). Great stuff.
Re: Your Pages Will Load Faster With Rails
#5This is just an ad for the guy's hosting business.
Re: Your Pages Will Load Faster With Rails
#6Wycats is a great guy and contributes a ton to the Ruby community, but I have to say...there's really not much here that's new or insightful. Set your headers, gzip content, and split assets across domains, yes, but - "Your pages will load faster with Rails"? Somehow the headline doesn't seem appropriate.
Hey @cscotta: This is just the first part of a few posts on this topic. The important part of the post is that Rails handles most of the heavy lifting for you. "Split assets across domains" sounds like it's a snap, but if you already have a large application and want to add it, it can be quite painful. The point is that with Rails, it's literally just a matter of adding a single line in your configuration and all your existing assets URLs will come along for the ride.
Same with far future expires. If you just set your headers to the far future, you'll be stuck with outdated content on the client that you can't control. If you use Rails, without doing a single additional thing, your asset URLs come prebaked with cache-busting behavior that operated in the background with no additional work by you.
Re: Your Pages Will Load Faster With Rails
#7This is just an ad for the guy's hosting business.
Huh?
Re: Your Pages Will Load Faster With Rails
#8I'd say download Firebug, YSlow, and Google's PageSpeed and let that be your guide, as these suggestions are helpful, but just the tip of the iceberg. A YSlow feature that is new (at least to me) is its JavaScript tab. It's not related to performance exactly, but it will run your JS through jslint, minify, beautify it (if it's in a gnarly style). Great stuff.
Totally the tip of the iceberg. I plan to post some more of the built-in Rails support for other YSlow recommendations in the coming weeks.
Re: Your Pages Will Load Faster With Rails
#9This isn't just specific to Rails. -Use Far-Future Expires -GZip Components -Split Components Across Domains
Of course not. But Rails makes it dead easy!
Re: Your Pages Will Load Faster With Rails
#10Wycats is a great guy and contributes a ton to the Ruby community, but I have to say...there's really not much here that's new or insightful. Set your headers, gzip content, and split assets across domains, yes, but - "Your pages will load faster with Rails"? Somehow the headline doesn't seem appropriate.
Hey @cscotta: This is just the first part of a few posts on this topic. The important part of the post is that Rails handles most of the heavy lifting for you. "Split assets across domains" sounds like it's a snap, but if you already have a large application and want to add it, it can be quite painful. The point is that with Rails, it's literally just a matter of adding a single line in your configuration and all you…
The title is misleading though because it makes it sound as if all you need to do to make your pages load faster is switch to Rails.
Whether or not Rails makes it easy to implement these suggests or if another framework makes it harder/easier is another discussion.