On Fri, Jun 25, 2010 at 3:41 PM, Gary Yngve <[email protected]> wrote:
> Merb currently requires use of extlib. Unfortunately, many other
> libraries depend on active_support because of the rails-centric ruby
> world, so it becomes a burden on the merbist to port libraries over
> just to get rid of the active_support dependency. Maybe it's time for
> Merb to be "support-agnostic" and allow for active_support or extlib,
> as DataMapper has done? (I'm ignorant to if this is happening in the
> 1.2 branch)
I'm facing the same issue, so far I've been able to patch some
libraries to be more restrictive in their use of AS so as not to stomp
on extlib but this is short term only. As much as I think AS is
bloated and awful I think you may be correct that it's time to
consider a hybrid or just a switch to it. It does look like recent
cleanups have made it easier to be selective in the AS pieces you use
("require 'active_support/all'" is evil).
Does anyone have an estimate on what it would take to do a hybrid vs.
just switching to AS? Any reason to keep extlib around if merb is the
primary (or only) user? I'd be happy to pitch in with this effort.
--Paul
--
You received this message because you are subscribed to the Google Groups
"merb" 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/merb?hl=en.
