Hacker News new | comments | show | ask | jobs | submit login

I wrote the article to explore what to do when your application is not wholly Rails. I got a lot of help and advice but I don't think there's full agreement on recommended practices yet. I've seen a range of opinion but a lot of advice doesn't hold up to analysis. The article reflects the best advice I've gotten.

Well thank you for compiling all of this together because about to deploy a new version of my product that has a significant amount of fairly complex JS and I found it very frustrating to not have any goto resource in regards to structuring and optimizing the code. I'm going to try and incorporate some of your tips and will report back if you'd like

You're welcome. Take a look at the link (in the article) to Ken Collins’s "Secrets Of The Asset Pipeline" slide deck. It's got some great recommendations about organizing your JS code. Let me know how it goes (you can leave comments).

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact