Rails 3.0 is a merge between Rails and Merb. The way the Merbists said to look at it is that Rails 3.0 is also Merb 2.0. (Merb 1.0 released a couple months before the merge was announced.) There's basically no reason to use Merb now that Rails 3.0 is almost done, but the merge brought many of the great parts of Merb to Rails.
Merb's main advantages were:Speed. Merb is faster and uses less RAM compared to Rails before the merge.Flexibility. Rails (pre-merge) is very opinionated.
You have to use the ActiveRecord ORM, for example. With Merb, it's extremely easy to use DataMapper or Sequel. Merb also made it easier to use HAML instead of ERB.
It's generators would generate HAML if you were using HAML, for example. Less "magic" in the codebase. Rails' code used a lot of weird idioms that helped its developers, but made the code more confusing to read.
Merb strived hard not to do this.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.