A question though: Several times throughout the article it talks about how Ramaze is not like Merb. However, based on the things they've said, it sounds a lot like Merb. (ORM agnosticim, for instance) Does anyone know how they actually differ?
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).