To @params or not to @params
Marcel Molina Jr. made mention earlier about using the params accessor method of the controller, rather than the previous @params attribute. Makes sense to me.
However, he also mentioned that the @content_for_* controller attributes have been deprecated in favour of using yield.
To be fair, this can only improve performance (a bit) by removing a layer and relying on Ruby rather than Rails, but I feel that it’s also removing one of the lovely syntactic sugary bits of Rails that makes it so easy to pick up, by having DSL features.
I’m sure in time there won’t be any difference in the minds of Rails developers, but it would be nice to be able to look back at old code (<%= @content_for_layout %>) and immediately think Oh yes, I remember, that displays the layout and content
rather than trying to mentally backtrace through Rails’ MVC framework (which will probably have become a lot more complex by then) and try to work out what yield is doing.