I think you confused Class::DBI for DBI earlier in the thread. For the sake of clarity - Ruby's DBI is a clone of Perl's DBI. ActiveRecord is a fairly run of the mill ORM which clones Class::DBI.

I think all of the MVC frameworks written in dynamic languages offer a clean and well integrated set with varying levels of polish. Maypole certainly provides seamless working in it's default combination of Maypole/CDBI/TT and also Maypole/CDBI/Mason.

I think the synergy you describe is certainly available in any decent MVC framework.

The biggest deal for me about Rails is it's highly polished marketing, documentation and evangelism, combined with a handful of well designed and good looking applications.

People moving from Java and PHP backgrounds will certainly see a productivity gain for smaller projects (I think for larger more complex applications Java would be equally productive for different reasons), but that isn't the case for those comparing Maypole or Catalyst to Rails.

In fact as far as I know, nobody has even mentioned switching to Rails from Maypole or even compared them, the only defectors we have had have been to Catalyst.

Right now, there simply isn't much of a reason to move from any MVC to another - they all provide their own advantages and I don't think we'll see much of the switching you seem to think is happening.

1 to 1 of 1

Ruby on Rails is only one option
2005-10-27 06:18:36
Curt Hibbs |
[View]