# Again plugins

**URL:** <https://www.ruby-forum.com/t/again-plugins/77106>\
**Category:** Engines\
**Created:** [November 24, 2006, 9:43am UTC](https://www.ruby-forum.com/t/again-plugins/77106 "2006-11-24T09:43:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hendy\_I](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/b4bc9f/32.png) [@Hendy\_I](https://www.ruby-forum.com/u/Hendy_I)\
**Post date:** [November 24, 2006, 9:43am UTC](https://www.ruby-forum.com/t/again-plugins/77106/1 "2006-11-24T09:43:07Z")

</div>

> **[アコムの審査は甘いのか他社カードローンと審査難易度を比較](https://www.iroop.jp/acom-shinsa/)**
>
> 最近、お笑い芸人の「かまいたち」がCM起用された馴染みある大手消費者金融のアコムは、初めての人でも利用しやすい消費者金融で、今までカードローンを使ったことが無い方におすすめです。 ですがもちろん誰でもお金が借りられる事は...

This is getting weirder. 99% of whetever written on that site is  
applicable to Rails Engines. I mean, if you follow almost every  
article there, but install Rails Engines instead of their plugins, I  
think it just works.

For now, the difference seems that an “engine” needs to be “an engine”  
(specially crafted). While in their version, all you need to do is  
just create a plugin, follow some conventions (like putting stuff in  
app/ subdirectory), and install the pluginaweek plugins (which are,  
well, 6 plugins?)

When Engines can get rid of the “Engines.start” thingy and allows  
easier creation of engines (i.e. not that much difference between  
plugins and engines, just follow some simple conventions like  
directory names)… how will Engines and pluginaweek matches? In my  
mind Engines will be just  
all-pluginaweek-plugins-built-inside-one-plugin or the other way  
around. Weird.

–  
Hendy I.  
Web: [http://hendy.gauldong.net](http://hendy.gauldong.net)  
Mobile: +62 856 24889899  
Yahoo Messenger: ceefour666  
LinkedIn: [http://www.linkedin.com/in/ceefour](http://www.linkedin.com/in/ceefour)

---

<div class="post-metadata">

**Author:** ![Hendy\_I](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/b4bc9f/32.png) [@Hendy\_I](https://www.ruby-forum.com/u/Hendy_I)\
**Post date:** [November 24, 2006, 10:39am UTC](https://www.ruby-forum.com/t/again-plugins/77106/2 "2006-11-24T10:39:14Z")

</div>

The 1.2 release will basically get rid of Engines.start, since Rails  
now includes a mechanism to control plugin loading order… hopefully  
that will stab the concept of ‘installing an engine’ in the heart, and  
everything will just be plugins again. Finally. It’s only taken about  
a year 🙂

---

<div class="post-metadata">

**Author:** ![Hendy\_I](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/b4bc9f/32.png) [@Hendy\_I](https://www.ruby-forum.com/u/Hendy_I)\
**Post date:** [November 25, 2006, 5:24am UTC](https://www.ruby-forum.com/t/again-plugins/77106/3 "2006-11-25T05:24:15Z")

</div>

On 11/24/06, James A. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> The 1.2 release will basically get rid of Engines.start, since Rails  
> now includes a mechanism to control plugin loading order… hopefully  
> that will stab the concept of ‘installing an engine’ in the heart, and  
> everything will just be plugins again. Finally. It’s only taken about  
> a year 🙂  
> so, what will happen with engines plugin?  
> what will happen with pluginaweek?  
> are they gonna join forces?

this sounds more like KDE vs GNOME to me.

–  
Hendy I.  
Web: [http://hendy.gauldong.net](http://hendy.gauldong.net)  
Mobile: +62 856 24889899  
Yahoo Messenger: ceefour666  
LinkedIn: [http://www.linkedin.com/in/ceefour](http://www.linkedin.com/in/ceefour)