Hi. - Scaffolding: I prefer it over django admin in many situations. I mean, when you're doing something complex you'll need to drop out the django admin and write your own code, so it's cool to have the basic CRUD code and develop from that. - Database ORM: Both orm (rail's ActiveRecord and Django's ORM follow active record pattern (http://www. martinfowler.com/eaaCatalog/ activeRecord.html) so...... they're not too different. - Migrations: I like the way migrations works in RoR. Django have some projects to work out on this but they're not as mature. - RoR controllers versus Django views: Django does not enclose in classes the controllers neither have Routes, the mapping between urls and views (plain functions taking a ``request`` object as first param. and then they receive too positionally the capturing groups in the regexps) is in files with paths and the module + function in python which dispatch them. RoR have Routes where you map urls and controllers, and controllers are classes. Also a huge difference is that in RoR, to have in scope variables in templates you declare variables as instance variables, in Django you pass them explictly in a Context object.
The conclusion is that they're different but very close. You can enjoy more using one or the other; but they provide with similar tools to achieve the same goals. On Dec 5, 1:06 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi All, > > I'm new to the django world and I was just wondering how Django > compears with Ruby on Rails ? > > did anybody try Ruby on Rails so can give us a feedback ? > > thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
