> "Merb/Rails Merge" started out as exactly that, a merge, it's now looking > more like just "the next version of Rails." To me, that says Rails is > adopting some "Merbisms" in to its next version, but Rails will maintain its > own identity separate from Merb and we really should think of the two as > separate projects each with their own pros and cons.
I am all for that, however I am curious to know where Merb has benefited from the merge. If all rails plugins would work in Merb, and vice versa, that would be good enough for me. -- 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.
