The way I see it, Merb is an implementation of Rails from the ground up- it appeals to Rails users and follows very similar conventions as far as configuration, directory structure, support for REST and included helpers (form_for, input_field, etc like in Rails)
Ramaze, on the other hand, is very Ruby oriented in its implementation- it follows KISS and POLS religiously. It does not force any convention on you, you are free to choose your own directory structure and there's no configuration files involved.
Agreed I love Ramaze's approach. And yes Tyler I agree with you on the terminal bit, my bad on that comparison. The point is that it's loads more fun to code in Ramaze as opposed to Rails. And I hope alot more people try it out too.
Ramaze, on the other hand, is very Ruby oriented in its implementation- it follows KISS and POLS religiously. It does not force any convention on you, you are free to choose your own directory structure and there's no configuration files involved.
Ramaze allows you to write an entire web-app in one file (see http://source.ramaze.net/source/examples/facebook.rb and http://source.ramaze.net/source/examples/ramaise.rb), which is not possible with Rails or Merb. Merb is great for RESTful applications and handles content negotiation very elegantly (with a simple 'provides :json, :xml' in your controller).