Gary Weaver
2013-Jun-25 16:54 UTC
Casting gem usage in Rails 4/Ruby 2 vs. Rails 4 push for concern usage/Rails delegation
Just read about the Casting gem: https://discuss.gemnasium.com/t/casting-adding-behavior-to-objects-without-using-extend/34 https://github.com/saturnflyer/casting What are the Rails core team''s opinions about using Casting vs. ActiveSupport::Concern usage, Rails delegation, etc.? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscribe@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.
Matt Jones
2013-Jun-25 17:15 UTC
Re: Casting gem usage in Rails 4/Ruby 2 vs. Rails 4 push for concern usage/Rails delegation
On Jun 25, 2013, at 9:54 AM, Gary Weaver wrote:> Just read about the Casting gem: > > https://discuss.gemnasium.com/t/casting-adding-behavior-to-objects-without-using-extend/34 > https://github.com/saturnflyer/casting > > What are the Rails core team''s opinions about using Casting vs. ActiveSupport::Concern usage, Rails delegation, etc.?Seems to me like AS::Concern and Casting deal with significantly different use cases: modular functionality at class-load time vs. modular functionality at runtime. Also, the benchmark noting the 100x speed difference compared to standard method dispatch is pretty hair-raising. --Matt Jones -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscribe@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.