Hi, I wanted to run small poll weather we should switch Merb to AS or not. Now it seems that voices which sounds in this google group wants to move over to the AS. At least how it looks, I'd like to hear more voices, really.
If the Yehuda already did removed the gem dependencies on the gems such as memcache etc which was big problem for me we can start with the either hybrid or pure AS changes. Yehuda wanted to remove these dependencies really quickly at least on the EuRuKo when we had opportunity to speak about that. Also there is a question if we need any external library such as Extlib or ActiveSupport. The DataMapper seems to get rid of the dependency on both and use it's own inflector. Maybe the way forward. My only concern is, saying it out loud, that I don't believe the Rails community to care about something outside the Rails at all. I do trust Yehuda but that unfortunately doesn't mean we won't get screwed by AS in the future. We can make the AS support, I'd vote for the hybrid one, happen in the 1.2 (which is current head). If we decide to remove the Extlib completely I'd like to do it in the 1.3 and leave some time (1.2 - 1.3) as a transition. Pavel On Jun 30, 10:11 am, jonah honeyman <[email protected]> wrote: > On Tue, Jun 29, 2010 at 01:37:08PM -0400, Paul Dlug wrote: > > 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). > > Same here :\ > > ActiveSupport's pervasiveness in gems is really getting to be > bothersome. Especially for libs that are only using AS for one or two > things like basic string manipulation. > > > 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. > > I started looking into it. It is getting more and more necessary to make > the switch to AS (IMHO, at least). While it is probably doable, merb is > so intertwined with extlib that it makes switching pretty annoying. > > I'll be happy to help out as well. Not sure where to start exactly. I > guess removing the dependency for extlib and working from there? > > In any event, this is a +1 for making the switch, or as Gary mentioned > allowing a choice like DM. It would be nice if PK & co. could pipe in > with whether this is realistic or not or if it is already on the agenda. > > > --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 > > athttp://groups.google.com/group/merb?hl=en. > > -- > -jonah -- 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.
