Just to follow up on my defense of IR, it was brought up in #roro again today and I ended up noticing that the author, Jose Valim, has formally deprecated it.
So, yeh, unfortunately, I'll have to rethink my usage of it now. I still disagree with a lot of the criticisms made toward it, and want to specify that Jose has said he's no longer continuing with it because he finds the responders gem along with Rails 3 to be a better solution for the problem. >From what I've gathered, seeing the responses made here and in channel on #roro, IR can easily be abused. So I suppose that's just the power of complexity. Cheers, Nicholas On Wednesday, May 16, 2012 10:54:32 PM UTC+10, Daniel wrote: > > On Tuesday, May 15, 2012 10:27:39 PM UTC+10, James Healy wrote: >> >> On 15 May 2012 17:23, Nicholas Faiz <[email protected]> wrote: >> > Inherited Resources. It's great. >> >> Personally I avoid inherited resources and devise like the plague. >> They're helpful for the simple case, but as soon as you start >> overriding the defaults you end up with control flow that's impossible >> to understand. >> >> +1 for inherited resources making things hard to follow. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To view this discussion on the web visit https://groups.google.com/d/msg/rails-oceania/-/x7pyjucH1GEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
