RailsConf 2011, David Heinemeier Hansson
Why Stack Overflow recommends it
Stack Overflow users link it when answering questions about Rails 3.1 asset organization and the Asset Pipeline, citing it as the framework creator's own explanation of the intent.
Recommended by 1 people across 1 different months, 2011 to 2011.
What it is
David Heinemeier Hansson, creator of Ruby on Rails, gives the opening keynote at RailsConf 2011. He walks through the upcoming Rails 3.1 changes, notably the Asset Pipeline and the new app/assets structure, along with the push away from RJS templates.
What people said
Recommends James Dunn · 2011-10 · Stack Overflow · on “Configuring Blueprint in Rails 3.1”
GTDev, I don't know anything about Compass, but I can show you how I'm using Blueprint with the new Asset Pipeline. It's woking well, and it feels like the Rails Way to me. First problem: Where does the blueprint folder go? Like many things in Rails, you have a few options, but some options are better than others. If you haven't already, I highly recommend that you take some time to watch the creator of Rails speak about the Asset Pipeline. [RailsConf 2011 Keynote] [this video] Anyway, so they created these empty folders in order to encourage the abstraction of stylesheets and javascripts, in terms of who wrote the code, and for what purpose. Whereas before, we treated them sortof as 2nd class ci
Cites awendt · 2011-05 · Stack Overflow · on “Where do app images get stored in Rails 3.1?”
Note: I haven't looked at Rails 3.1 yet... As far as I understood DHH's keynote [this video] , app/assets was introduced so you could structure your application in a better way. But there's nothing wrong with storing images in public/images . Thanks to Michiel for pointing out that public/images will no longer be with us in Rails 3.1!
Cites numbers1311407 · 2011-08 · Stack Overflow · on “Is it correct to have files that mix Javascript and ruby? ie. (.js.erb)?”
RJS templates were essentially the way things were done for a long time, which is why you still see such a prevalence of the technique in tutorials. That being said, as you've noticed, they're on the way out, and with good reason. I'm sure there are many reasons why RJS templates are a very bad thing , but a big one is how tightly they couple your view JS to your view HTML. Many problems arise from this, a few being: Lack of flexibility. Using your bit of code as an example. What if you wanted to be able to create posts from a different view? And have a different effect? Maybe there's no <table> on the page at all and you just want to pop up a "success" message? Etc. What if you just wanted