Merb to be merged into Ruby on Rails 3. Neat.
Having source and a permissive license available is good for the health of a project for two reasons: if everyone deserts it, it can be picked up and continued; and if it starts focusing on the wrong thing, it can be forked and continued. Having parallel projects are good to the extent that they focus on different things.
Merb and Rails have different outlooks but their implementations by necessity overlap greatly. Their different focus is mostly the result of a slightly different mindset. From the beginning, Rails was extracted from a product, and the decoupling has been a continual process. If Rails is decoupled further, the parts of the framework that you have to use will be able to shrink and you’ll be able to plug in parts to a much greater extent, fulfilling Merb’s stated difference from the Rails philosophy. This can happen while Rails continues to act like Rails. Assuming they can pull this off, Rails and Merb users both benefit and there’s no duplication of effort.
Moreover, I advise that the iPhone software platform must be opened.
No comments yet.
Sorry, the comment form is closed at this time.