Sorry for my rudeness.
I really appreciate rails core team who bring and maintain the great
rails framework. I learned and benefited a lot and a lot.
as merb is coming out, its purpose and strategy overlaps with rails
As I know, it was borned for rescue some old rails shortcomings,
I dived into codes of both, for now, rails still have some
architecture problems, while merb is clean but young.
Since rails core team is always exposing courage to throw dirties
away, is there any plan to merge merb and rails into one big thing?
In my opinion, merb is more like rails 3.0 after a throughout
By the way, I play with merb at part time and use rails for work.
I digged nearly every corner of rails source code to add my
extensions. for example,make STI accept foreign_type_mapping to
customize the mapping between column value and subclass name.
I suffered a lot to hack rails code everywhere for customize it. I
really think that rails need a throughout refactory before I met merb.
(I offered little feedbacks to community because we are basing on
rails 1.2.6, please forgive me for that. and I posted several tech
articles to native language forums)
I know there are lots of problems if merge them together: technique
reason, preference reason, politics reason…
Ezra Z. said 6 days later:
@Kevin- At this point merb is not going anywhere. If the rails core
team wanted to get radical and decide to build rails 3.0 on top of
merb-core technology then I might consider merging the two projects.
But I think that would take a lot of politics and I’m not sure if they
would agree to it. So don’t fret, merb is here to stay unless the
rails-core has a drastic change of heart. And the code base for merb
is way more simple and scalable for the future since it has no
baggage. So expect merb to stick around and innovate for a long time
to come. I just figured that there is no reason for everyone using
Rails to suffer when I could spend a few weeks and improve a bunch of
stuff for folks.
Anyway, Is there any possibility to merge them?