First of all, I totally agree with this message.  But I think you
should be careful about saying the problem should be solved in the
Rails core.  The core team's distaste for high-level components, is
well-known and well-justified.

The crux of the matter is that the mechanics of modular code don't
have a standard best-practice solution.  Every component system has
it's own requirements.  There can be no one-size-fits-all solution.
And if you look at Rails, it's pretty good at sticking to best
practices and solutions that work in the vast majority of cases.

So rather than say that Rails core should solve this problem.  I would
say Rails core should SUPPORT THE SOLVING OF this problem.  Modular
development is going to happen on top of Rails simply because it's
such an awesome infrastructure.  I believe the core team can support
that kind of development with a few patches here and there without
comprimising the original focus or cleanliness of the Rails codebase.

Just to give an example, if John develops this plugin as-is, there
could be a performance problem with adding too many things to the load
path.  A good patch to solve that would give Rails a more efficient
way to look for these files according to a new naming convention.
Such a patch would be minimally disruptive to Rails, but could open up
whole new avenues for development on top of Rails.


On 6/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

> Plugins are the beginning of code sharing, but they simply aren't
> powerful enough (no direct support for views, routing, database
> migrations, public assets, etc).  This is a problem that many people
> have tried solving in one way or another (Plugin-a-week's
> appable_plugins, Rails Engines, RHG's Plugems, Radiant's extension
> system, etc) but really should be discussed and solved at the core
> level.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to