# Acts\_as\_taggable : plugin vs gem **URL:** \ **Category:** Rails\ **Created:** [February 11, 2006, 6:21am UTC](https://www.ruby-forum.com/t/acts-as-taggable-plugin-vs-gem/53605 "2006-02-11T06:21:48Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![aravet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/49beb7/32.png) [@aravet](https://www.ruby-forum.com/u/aravet)\ **Post date:** [February 11, 2006, 6:21am UTC](https://www.ruby-forum.com/t/acts-as-taggable-plugin-vs-gem/53605/1 "2006-02-11T06:21:48Z")
Googling for acts\_as\_taggable is a little confusing: gem, plugin?! What are the differences? Which one to choose? Where is the best doc? Alain ---
**Author:** ![aravet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/49beb7/32.png) [@aravet](https://www.ruby-forum.com/u/aravet)\ **Post date:** [February 11, 2006, 6:40am UTC](https://www.ruby-forum.com/t/acts-as-taggable-plugin-vs-gem/53605/2 "2006-02-11T06:40:59Z")
plugin requires Rails 1.1, so unless you’re running Edge it won’t work. Also, there is no documentation as yet. Gem works on 1.0. It has some documentation, but as far as I can tell the real meat of the docs was ([http://dema.ruby.com.br/articles/2005/09/03/tagging-on-steroids-with-rails](http://dema.ruby.com.br/articles/2005/09/03/tagging-on-steroids-with-rails)) which unfortunately doesn’t seem to exist anymore. I’d love to be shown otherwise, I only started checking out acts\_as\_taggable a few days ago. They work pretty much the same, but are implemented differently. plugin is eaiser to configure since it’s one line to make it works, and seems simpler to use in general. Bottom line, if you’re not using Edge you can’t even use the plugin now anyway…when Rails 1.1 comes out you should be able to convert it all somewhat easily using migrations. Pat ---
**Author:** ![aravet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/49beb7/32.png) [@aravet](https://www.ruby-forum.com/u/aravet)\ **Post date:** [February 11, 2006, 7:28am UTC](https://www.ruby-forum.com/t/acts-as-taggable-plugin-vs-gem/53605/3 "2006-02-11T07:28:49Z")
The current code and documentation for acts\_as\_taggable gem is here: [http://rubyforge.org/projects/taggable/](http://rubyforge.org/projects/taggable/) It is very confusing that someone came up with a plugin of the same name instead of taking the existing code and changing the implementation of the pre-existing gem code. Two completely different instances of acts\_as\_taggable will only cause pain down the road. My cloud code (the second link of a Google search for acts\_as\_taggable!) has only been tested with the Gem code. ---
**Author:** ![aravet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/49beb7/32.png) [@aravet](https://www.ruby-forum.com/u/aravet)\ **Post date:** [February 12, 2006, 11:38pm UTC](https://www.ruby-forum.com/t/acts-as-taggable-plugin-vs-gem/53605/4 "2006-02-12T23:38:18Z")
> So, what’s the verdict? > Which one has the best future? > Which one has the best features? The plugin was written by DHH, so that’s probably the future. There are basic docs in the new Pragmatic Rails Recipe’s beta book. It is confusing, agreed. ---
**Author:** ![aravet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/49beb7/32.png) [@aravet](https://www.ruby-forum.com/u/aravet)\ **Post date:** [February 13, 2006, 1:50am UTC](https://www.ruby-forum.com/t/acts-as-taggable-plugin-vs-gem/53605/5 "2006-02-13T01:50:38Z")
I would go with the GEM right now because it works with any Rails version, is documented, and people have experience with it. In 3 months time, this may change. ---
**Author:** ![aravet](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/49beb7/32.png) [@aravet](https://www.ruby-forum.com/u/aravet)\ **Post date:** [February 12, 2006, 10:38pm UTC](https://www.ruby-forum.com/t/acts-as-taggable-plugin-vs-gem/53605/6 "2006-02-12T22:38:06Z")
Tom F. wrote: > It is very confusing that So, what’s the verdict? Which one has the best future? Which one has the best features? Alain