Seeing as you asked ;) You're kidding, right? Have you been (working) in the industry long? Seriously. That sounds like a great answer from an incredibly intelligent really good, ace rails programmer but not really related to business needs. Ask any business person and always know that they pay the bills :) I genuinely would welcome a good - business - justification as to why 12 months is deemed an appropriate length of time. Why not 36 months? Also why not better error messages generally? I and many others need something that is around for longer than a year. Applications, books, references, etc. should not all just become 'invalid' after 1 year and no longer have helpful warnings. and I'm at a loss to understand why to remove something helpful? Changing new docs, the api, etc that's all great and I totally support it, it's the rails/open way after all to constantly improve, but break an old thing within a year or 2, I don't get it. 'bloated api' reason? I think we have the space now. See above, rinse, repeat. But again, more income for us, right? There's no substitute for business experience, but of course you can lead a horse to water... Thoughts?
>> > A deprecation warning was added in 1.2.0 (http://github.com/rails/ > rails/blob/v1.2.0/actionpack/lib/action_view/helpers/ > form_tag_helper.rb) and then that method was removed almost a year > later. What more do you want? > > Fred -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
