# Why RoR needs plugin?

**URL:** <https://www.ruby-forum.com/t/why-ror-needs-plugin/107792>\
**Category:** Rails\
**Created:** [June 26, 2007, 11:08am UTC](https://www.ruby-forum.com/t/why-ror-needs-plugin/107792 "2007-06-26T11:08:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![chamnap](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/779978/32.png) [@chamnap](https://www.ruby-forum.com/u/chamnap)\
**Post date:** [June 26, 2007, 11:08am UTC](https://www.ruby-forum.com/t/why-ror-needs-plugin/107792/1 "2007-06-26T11:08:57Z")

</div>

Hello,

I am new to RoR. It seems that it needs more and more plugins. Why it  
is like that?

Thanks  
Chamnap

---

<div class="post-metadata">

**Author:** ![chamnap](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/779978/32.png) [@chamnap](https://www.ruby-forum.com/u/chamnap)\
**Post date:** [June 26, 2007, 12:45pm UTC](https://www.ruby-forum.com/t/why-ror-needs-plugin/107792/2 "2007-06-26T12:45:12Z")

</div>

Im no expert, but I believe it is because Rails is supposed to provide a  
basic framework to get a site running. The plugins are needed for  
adding in  
the functionality you are going to use.

It’s a good thing in my opinion.

Richard

On 6/26/07, Chamnap [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> >

–  
Richard J Hancock  
Developer/System A.

---

<div class="post-metadata">

**Author:** ![chamnap](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/779978/32.png) [@chamnap](https://www.ruby-forum.com/u/chamnap)\
**Post date:** [June 26, 2007, 1:04pm UTC](https://www.ruby-forum.com/t/why-ror-needs-plugin/107792/3 "2007-06-26T13:04:13Z")

</div>

Generally speaking, plugins provide special features for special usage  
scenarios.  
Building all of those features into Rails directly would make the  
Framework too big and clumpsy

Also, Plugin often offer different ways to achieve the same thing, so  
the developer can choose which way he prefers.  
It would be impossible to build all those into rails at the same time,  
as they would conflict.

---

<div class="post-metadata">

**Author:** ![chamnap](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/779978/32.png) [@chamnap](https://www.ruby-forum.com/u/chamnap)\
**Post date:** [June 26, 2007, 8:25pm UTC](https://www.ruby-forum.com/t/why-ror-needs-plugin/107792/4 "2007-06-26T20:25:13Z")

</div>

As a framework (or any general-use project) grows, it becomes more and  
more complicated as features are add. Many Java stacks are needlessly  
complex simply because they have grown to attempt to do everything  
over the years. This makes the simple cases much harder than they  
need to be. The Rails Core team is extremely aware of this, and is  
focused on only adding widely useful bits to core, and keeping  
everything else in plugins. Even pulling things from core out into  
plugins where it makes sense. This keeps Rails lean and mean.

---

<div class="post-metadata">

**Author:** ![chamnap](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/779978/32.png) [@chamnap](https://www.ruby-forum.com/u/chamnap)\
**Post date:** [June 27, 2007, 4:34am UTC](https://www.ruby-forum.com/t/why-ror-needs-plugin/107792/5 "2007-06-27T04:34:07Z")

</div>

Chamnap wrote:

> I am new to RoR. It seems that it needs more and more plugins. Why it  
> is like that?

Good question, because the answer is simple yet subtle.

Ideally, in a software platform, you don’t “pay for” what you don’t use.  
That means (even if the platform is free to download), you don’t pay  
programmers extra time to go around the features they don’t need.

If Rails had one default way to do a Calendar, and if programmers needed  
a  
different way, they should pay twice, once for the default Calendar and  
again for another one.

So the ideal platform allows you to plug in all the components you need,  
and  
leave out the ones you don’t. This, in turn, requires Rails itself to  
represent the smallest set of the best modules that make it Rails.

And some of the current Rails modules will be taken out in Rails 2.0,  
and  
moved into plugins.

–  
Phlip  
[Test Driven Ajax (on Rails) [Book]](http://www.oreilly.com/catalog/9780596510657/)  
“Test Driven Ajax (on Rails)”  
assert\_xpath, assert\_javascript, & assert\_ajax

---

<div class="post-metadata">

**Author:** ![chamnap](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/779978/32.png) [@chamnap](https://www.ruby-forum.com/u/chamnap)\
**Post date:** [June 26, 2007, 9:12pm UTC](https://www.ruby-forum.com/t/why-ror-needs-plugin/107792/6 "2007-06-26T21:12:24Z")

</div>

This is one reason I prefer Ruby on Rails over just about any other  
frame  
work in any language I’ve used. Nothing I don’t need, but every thing I  
do  
need is lurking about some where. Amazing.

Nathan Garza

AshLeaf Media | Director of Technology Innovations

* * *

[www.ashleafmedia.com](http://www.ashleafmedia.com) | removed\_email\_address@domain.invalid | 832.514.5726
