Hacker Newsnew | comments | show | ask | jobs | submitlogin

Yes I guess that would be the right metric. You'd need to look at average time to render over a number of deploys with both strategies. I'm pleased to see articles approaching this subject as there's definitely not enough solid discussion around this.

One other optimization you may want to talk about in your next article is to use a gem like the asset_sync gem to upload your assets to S3 or CloudFront (or similar) at compile time.




I'd like to look deeper into this option. I didn't mention it in the article, but @jo_liss suggested hosting all assets on CloudFront in production. She points out that you can set up CloudFront and get your own content-delivery network in five minutes. Once you have your own CDN, there's no advantage to using any 3rd-party JS host.

-----


That's somewhat true. However, using Google does have an advantage over your own CDN -- it's more likely to already be cached in someone's browser.

On these occassions the hit to download JQuery (or something big like JQueryUI) is zero.

This is more a consideration for a landing page than a heavy-use application though.

-----




Applications are open for YC Summer 2015

Guidelines | FAQ | Support | Lists | Bookmarklet | DMCA | Y Combinator | Apply | Contact

Search: