This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have done rails work in the past. How much of a learning curve is in store for me as I look into merb? If the learning curve is steep I might consider a more barebones approach like Sinatra, especially for simpler site work.
Ah, if you're comfortable using Rails, I'd say definitely stick with it.
However, just so you know, the learning curve going from Rails to Merb is pretty gentle. In fact, a lot of the stuff in Merb might just make more sense than it ever has in Rails. This is because of Merb's strong adherence to the Principle of Least Surprise. Anyway, why then stick with Rails? Well, I'm keen on conserving one's energies, and Rails3 is going to be where all the development action will be happening anyway. If you're still looking for some Merb awesomeness all before the official Rails3, be sure to check out Rails edge and maybe drop in DataMapper in place of ActiveRecord. It's an amazing ORM and really made me love the default Merb stack. Alternatively, if you've got a small app that may have been better suited for a single file Merb application, do take a look at Sinatra. Its inherited a lot of Merb goodness and a great way to explore Rack middleware.
Hey there Foy, can you help me better understand Rack? I've heard it mentioned a lot, but haven't progressed to the point of being able to use (or need) it just yet. What problem does it address? I've heard of it being used in situations where speed/throughput was more of a concern, but not sure if this was it's intended purpose.
Also, what advantages does DataMapper have over ActiveRecord (which I've found to be quite pleasant to use)?