To answer Abdur's question - as I understand it, the core team want to
keep the plugin system very simple, and while there are some
mechanisms to handle plugin 'dependencies' (the private method
'load_plugin', for example - I can't find the Ticket that discusses
this in its comments), there has also been (understandable) resistance
to implementing any form of dependency management.
If you need something more 'advanced', you'll need to either make the
extensions yourself, or use something like the Engines plugin.
The point of David's post was extolling the pitfalls of trying to
create generic components that are a *one-size-fits-all solution*
("The trouble with high-level components are solely related to making
them generic."). I don't think anyone would disagree with that.
However, it's important to note that you could quite easily replace
every instance of the word 'engines' with 'generators' or 'plugins'
and the spirit of his post would be literally untouched, since
although the scope their functionality differs, the purpose of each of
these development tools is the same: code reuse. There is simply a
balance to be found between religious adherence to the DRY principle
and writing custom code for everything.
It makes me more than a bit sad when people misunderstand what he
wrote, but then this isn't the place to convince you otherwise.
james
On 12/30/05, Deirdre Saoirse <[EMAIL PROTECTED]> wrote:
>
> On Dec 29, 2005, at 10:47 PM, Nathaniel S. H. Brown wrote:
>
> > I still stand behind my recommendation. David may be the seed by
> > which Rails
> > has flourished, but it is not necessarily, and it is not beneficial to
> > follow blindly where other paths have great rewards.
>
> [...]
>
> > I understand where David is coming from, but there are more minds and
> > opinions to share in the growth of the framework.
>
> Except, of course, this is the rails-core list. David's already made
> his point on the subject.
>
> --
> Deirdre Saoirse Moen http://deirdre.net/
> [EMAIL PROTECTED]
> "Let's make an app that does pretty pretty log log."
>
> _______________________________________________
> Rails-core mailing list
> Rails-core@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails-core
>
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
