Hi Glenn, I'd have to second Patrick's vote. _on_steriods seems to be sticking around pretty well. For most tagging things I've done lately I've just build a has_many through association instead of using a plugin. I go to the plugin if I've need tag clouds or such.
History lesson if anyone is interested in why there are two plugins named the same, but with different features: In the beginning there was Acts As Taggable gem. This gem is a valid Rails plugin, its just also packaged up as a gem. I used it in several projects back in the day (wow that was only 2 years ago!?) This was put together by Dirk and quite a few people where using it. When Polymorphism and has_many_through came out DHH released the acts_as_taggable plugin and caused all the confusion. A lot of folks took him to task for not bothering to google the name before he used it. He claimed he know about the other gem, but that since they had the same (or similar) functionality that he thought it was right that they had the same name. Several people started referring to the plugin as acts_as_asshole at that point. Around that time acts_as_taggable_on_steriods and several other solutions showed up. Confusion reigned. Rob On Thu, Dec 11, 2008 at 11:51, Patrick Crowley <[email protected]> wrote: > >> Is there any consensus pick? It's not clear from >> googling and looking at repositories, but it seems like >> there's a slight preference for "acts_as_taggable_on_steroids" > > I'd recommend acts_as_taggable_on_steroids, Glenn. > > That's what I'm using on Graffletopia, and I believe the number of > available tweaks and variants indicate this is the mainstream choice > for tagging plugins. > > -- Patrick > > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
