Use of Ruby Gem and Plugin

Hi
I shall share what I know Anyone please correct if I am wrong

I think when a plugin stabilizes it goes to form gem .In case of plugin
the code is with your railsProject So you dont need to install it on
server again.And one thing it has to be loaded when you start the
project So that much memory is needed. Reverse applies to a gem to an
extent

Sijo

Sijo Kg wrote:

Hi
I shall share what I know Anyone please correct if I am wrong

I think when a plugin stabilizes it goes to form gem .

Often, but not always.

In case of plugin
the code is with your railsProject So you dont need to install it on
server again.

And you can do the same thing with a gem if you freeze it.

And one thing it has to be loaded when you start the
project So that much memory is needed. Reverse applies to a gem to an
extent

I'm not sure if this is at all accurate.

Basically, gems seem to me to be best for extensions that you're going
to use on many projects. Plugins seem better for packages that you'll
only be using on one project. I know there is a current trend toward
gems and away from plugins; I'm not convinced that this is a good idea
in all cases.

Sijo

Best,