padrino-vs-merb.rdoc

Merb¶ ↑

• Has routes.rb like rails, Padrino not

• Merb define controllers in class and routes in def like rails, Padrino use sinatra blocks.

• Merb has not admin, Padrino has some thing like django-admin

• Merb has slices that are 1:1 equals to Rails Engines, Padrino apply the same concept of DJango where you build a project and then apps.

• A full merb stack require some like 56 gems Padrino if Im not wrong 16 gems.

• Padrino has full support to I18n like rails/django, Merb not

• Merb has DataMapper as preferred orm, Rails ActiveRecord, Padrino “NONE”

• Our rendering is only an enhanced version of Sinatra rendering (but Merb didn’t support haml :foo, erb :bar)

• Merb was not designed to be a multi-app project

• Merb light-weight more than rails but trust me it’s more more bigger than Padrino.

• Padrino like sinatra can define app conf every where.

• Merb use before/after filters as rails do, Padrino some thing very very different.

• Padrino has route conditions Merb (if I remember correctly not)

• Directory structure of Merb is equal to Rails structure. Padrino has their own structure (designed for multi-app purpose)

• Merb is Agnostic, Rails 3.0 is agnostic, Padrino is really agnostic (because we don’t need 3th party gems for adapters/test/scripts etc…)

About the routes, have you guys seems hassox's pancake? It's pretty interesting and in some ways it has slightly similar approach as yours I think.

About your arguments, routes are a different thing, that's for sure. But if there is a default ORM or not, it's not really an argument, because in Merb you can configure it anyway. I don't know what are route conditions, but if you mean deferred routes, Merb have them. Merb router is still the best router out there and I'm telling it as a Usher contributor :)

Anyway I have quite a similar approach in Rango in some stuff. Currently I'm thinking about mountable applications and it's pretty hard thing to do right.

About the routes, have you guys seems hassox's pancake? It's pretty interesting and in some ways it has slightly similar approach as yours I think.

Yep yes I know pancake and also they follow Sinatra routing definition.

But if there is a default ORM or not, it's not really an argument

I think this important because is also for DM that Merb ships with ExtLib.

I don't know what are route conditions

Take a look here: http://www.padrinorb.com/guides/controllers#custom-conditions

Merb router is still the best router

Me too, but Im not a super fan of routers files I prefer our way: mapping during definition.

Anyway I have quite a similar approach in Rango in some stuff. Currently I'm thinking about mountable applications and it's pretty hard thing to do right.

Yep I know your framework, and yes mountable apps are very tricky to manage due also to the fact that for example Passenger is not full prepared for that. Btw we do the best for make it simple as django do.

I think main difference between framework are the "why" are built.

• Django - press sites
• Rails - for 37 signals
• Merb - for be a fast rails

Padrino?

Personally I've a society and we build some like 100+ sites considering my experiments some like 300+ apps. For this reason I built (with Nathan and Arthur) some thing that simplify our life and in the meanwhile give us some thing new to write, really tiny, clean and concise. As we say in our way page for us coding is also an "art form" and we try to do the best for follow this way.

I think both Merb/Rails are high level framework and for example hack (for some reason) ActionController/Dispatch is not super simpler with Sinatra/Padrino is very intuitive (I think). So in this way I hope any web-developper can fits this framework for their own needs.