Yay. We always see opensource branch and branch. Rarely do we see them come together.

Merb is an open, ever-changing project, and some its best ideas have come from not-core regular-Joe community members. It’s gotten where it has because of the community, and the community will get us even further in the future. Your ideas, feedback and even complaints will be 100% welcome in the future, just as they have been in the past. I believe in the tremendous value an open community and just generally open attitude bring to the table, and am counting on those things to continue ushering in the future of Ruby.

On to the news: beginning today, the Merb team will be working with the Rails core team on a joint project. The plan is to merge in the things that made Merb different. This will make it possible to use Rails 3 for the same sorts of use-cases that were compelling for Merb users. Effectively, Merb 2 is Rails 3. (Source: Yehudakatz)

I don’t use Rails by the way. I use more of CakePHP. But anyway, I think the merger is a good direction. Of course this is arguable since the merger would mean one less competing Rails framework. But this is software, not business. Merger means greater understanding. I believe there are many ways of doing one same thing, but one way that would be most efficient in most given situations and that’s why people build frameworks.

comments powered by Disqus