I'd like to chime in and say that I am still happily building apps
with merb, http://engineyard.com/solo is built on merb. I don't find
that there is anything I'm missing or that there are any features or
major bugs stopping me from building apps with merb.
If merb works for you then use it, it is very stable and runs well in
production. If you need the newest shiniest features all the time then
rails is probably getting more love these days and may be a better
option for you.
I'll let Yehuda and Matt chime in on the other questions specifically
but I just wanted to say that merb is solid as is, it works and runs
very well in production. I think merb is kind of feature complete and
extensible enough that you can build whatever you want with it as a
Ezra (happy merb user)
Note from Publisher: Because Rails 3 in Action is replacing Merb in Action, if you order now, we'll send you the chapters developed so far for Merb in Action, and you'll start receiving new chapters based on Rails 3 as soon as they become available.
In December 2008, the Merb team announced that they will be collaborating with the Rails core team on the next versions of Merb and Rails. Rather than maintaining parallel tracks, Merb 2 and Rails 3 will merge, preserving the flexible configuration and advanced features that Merb users love along with the rapid productivity and ease-of-use that makes Rails shine. As Engine Yard developer (and Manning author) Yehuda Katz puts it, "Effectively, Merb 2 is Rails 3."
The thing I'm more concerned is the 1.1 release we were promised and even more important, the "easy" upgrade path to rails 3 we were promised by releasing several versions of merb that would deprecate poco a poco the old api to make it more simple to upgrade to rails3. At least that's what I remember from the blog posts announcing the rails+merb merge but I might be wrong.
It doesn't suck at all, it just helps to have perhaps bi-weekly
(monthly?) updates on what's going on - even if it's just "we're still
working on blah" ;-)
The communication is key. We DEFINITELY realise that the ground is
different than a map of the ground.... so any anticipation vs reality
is most likely going to differ from each other...
* Yehuda Katz <wyc...@gmail.com> [2009-06-28 22:31:54 -0700]:
> The promised post.
I would like to ask this question to all Merb developers specially ...
(1) Yehuda and (2) Matt from Merb Core Team.
Pl. be frank and honest.
Question 1:- Is Merb 1.1 really coming, or plans are dropped
Question 2:- Will the Merb progress die after Rails 3.0
Question:- Why there are no updates on Merb Information and Merb
Question:- Is Merb Core Team willing, All Merb developers should shift
to Rails 2.3.2 as soon as possible...?
Question:- Which great asests of Merb are coming in Rails 3.0..?
Question:- Should we stick to Merb or move away to Rails as soon as
in fairness to the Merb core team who graciously puts out great stuff,
I'm not sure some of you truly understand how open source works, but
you're really encouraged to get involved. Code agendas are set by those
who write code - albeit, most contributors are happy to take
suggestions. If you don't wish to contribute, then you're free to
simply take advantage of whatever comes along (I'm guilty of frequently
doing this), but if you WANT certain features, then it's up to you to
take the initiative and just do what you can and commit. In this case,
if you're using Merb, then you're certainly capable of writing a blog or
probably better, adding a wiki page yourself - I'm sure that whatever
help you need to post it at the merb web site will be forthcoming. By
doing some of the grunt work yourself, the core team can concentrate on
more difficult tasks.