From: Matthew Desmarais Date: 2006-01-14T09:22:28+09:00 Subject: Re: Questions to Forward (was Re: why is this a comile error) Gregory Brown wrote: > On 1/13/06, James Edward Gray II wrote: > >> On Jan 13, 2006, at 4:59 PM, Austin Ziegler wrote: >> >> >>> On 13/01/06, James Edward Gray II wrote: >>> >>>> On Jan 13, 2006, at 3:17 PM, Austin Ziegler wrote: >>>> >>>>> This is better posted to the Rails list: >>>>> http://lists.rubyonrails.org/mailman/listinfo/rails >>>>> >>>> Is it, this time? >>>> >>>> I know this has become our standard response, but the issue above is >>>> a Ruby syntax mistake. It has nothing to do with Rails. Is that not >>>> squarely in our area of expertise here? >>>> >>> Yes, it's a Ruby syntax mistake. However, it's *not* code that's >>> runnable without Rails. >>> >> I see a lot of code posted here that requires external libraries and >> we fix that. Is there a reason Rails is different? >> > > I'd say that it's the fact that Rails already has a large support > community that we should point them in that direction. A lot of > libraries aren't as easily supported, as if the developers may not get > to the questions in a timely fashion, etc etc. > > I think though it seems a bit harsh, sending people to the Rails > mailing list actually does a service, rather than a disservice. If > they did not know it existed before, they find a great new resource, > otherwise, they just know where to ask next time. > > Though, I usually try to offer whatever help I can with a question, > THEN point people to the rails list, just to be nice ;) > Once again, GBrown beats me to it. I agree. If a person wants to use Rails to build their web app and they aren't interested in the Ruby that Rails is built in, I'm comfortable with that. Referring them to the Rails list where they can talk Rails without having to filter out all of the noise about that "Ruby" thing is the best we can do. If, on the other hand, they want to fix up some Ruby code or learn more about what makes Rails tick then I think they've come to the right place. I'll be surprised on the day that I see this list turn someone away that needs help with their Ruby code just because it's for use in a Rails app. Matthew